This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html)
- To: Jim Wilson <wilson at cygnus dot com>
- Subject: Re: $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html)
- From: Jason Merrill <jason at redhat dot com>
- Date: 21 Jul 2000 14:19:27 -0700
- Cc: Geoff Keating <geoffk at cygnus dot com>, hjl at lucon dot org, aoliva at cygnus dot com, gcc-patches at gcc dot gnu dot org, binutils at sourceware dot cygnus dot com
- References: <200007211854.LAA21292@wilson.cygnus.com>
>>>>> Jim Wilson <wilson@cygnus.com> writes:
> There are certainly differences in the build process. HJ doesn't like
> to use the --with-headers= and --with-libs= options that we recommend.
I don't see how those options would help; as far as I can tell, all they do
is copy the headers and libs from the specified locations into $(tooldir)
and suppress newlib. They don't seem to affect at all how the headers and
libs are found.
When you build an ia64 toolchain, where does your crt0.o live? How does
the compiler find it?
Jason