This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Information Request

From: James E Wilson <wilson at specifixinc dot com>
To: "alex19_82 at libero dot it" <alex19_82 at libero dot it>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 09 Sep 2004 15:32:40 -0700
Subject: Re: Information Request
References: <I3RQTE$EEA04DFD0F435328E4286EB8A3AA65EB@libero.it>

alex19_82@libero.it wrote:

/users/students/tesi08/tools/lib/gcc-lib/powerpc-eabi/3.3.4/../../../../powerpc-
eabi/bin/ld: warning: cannot find entry symbol _start; defaulting to 01800074

You have to provide a linker script and libraries. This stuff is sometimes refered to as a board support package (BSP).

The powerpc-eabi compiler supports many different embedded target boards. Code has to be linkedly differently for them, because of hardware differences. For instance, they may have RAM located at different places in the address space.

If you just want to emit code for the (gdb) simulator, try -msim. See also the documentation, which lists a bunch of other -m options for other hardware/simulator choices.

A good way to learn about the options needed for various targets is to look at dejagnu. For instance, on a linux system with dejagnu installed, look at /usr/share/dejagnu/baseboards/powerpc-sim.exp which tells you that you need the -msim gcc option when linking. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- Information Request
  - From: alex19_82\ at libero\ dot it

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]