This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: Which libgcc?
- To: Kenneth Porter <kenneth_porter at kensingtonlabs dot com>
- Subject: Re: [ECOS] Which libgcc?
- From: Jonathan Larmour <jlarmour at redhat dot co dot uk>
- Date: Fri, 04 Feb 2000 20:15:21 +0000
- CC: "ecos-discuss at sourceware dot cygnus dot com" <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <200002041912.LAA16379@obi-wan.kenlabs.com>
Kenneth Porter wrote:
> I guess my question really amounts to what to put in the -L flag. I
> need to tell ld where to look for libgcc.a, and I don't know if I
> specify a directory higher up the tree or the specific subdirectory for
> the architecture I'm building to.
You shouldn't need to. It should be in default link path already, and
target.ld contains the directive "GROUP(libtarget.a libgcc.a)" which means
you don't need to specify -ltarget -lgcc on the link line either.
> Will do. I'll also try the gnu.gcc.help newsgroup. I'm kinda unsure
> where the best place to ask about cross-compilers is, whether there's
> more knowledge here on the eCos list or over on the gcc list, as I
> expect the gcc list would deal more with native compilers on Unix
> systems.
Many people who deal with cross-compilers (myself included) read the gcc
list, so don't worry on that front. There's also
crossgcc@sourceware.cygnus.com. Go to http://sourceware.cygnus.com/ml/ for
info on how to subscribe.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault