This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Always link against static libgcc on hppa-linux
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
- Cc: law at redhat dot com, dje at watson dot ibm dot com, mark at codesourcery dot com,rth at redhat dot com, gcc-patches at gcc dot gnu dot org
- Date: Thu, 14 Feb 2002 22:21:58 -0500
- Subject: Re: Always link against static libgcc on hppa-linux
- References: <3123.1013730256@porcupine.cygnus.com> <200202150003.g1F03oJg004338@hiauly1.hia.nrc.ca>
On Thu, Feb 14, 2002 at 07:03:50PM -0500, John David Anglin wrote:
> > > I am sure it could. In that case, should binutils build and install
> > > the library?
> > Why would binutils build/install that library? Wouldn't it be either a
> > separate package or part of glibc package?
>
> Simply, binutils needs to be built first before anything else. If the
> linker is to automatically link this library with everything, I don't
> see conceptually that this is significantly different from it adding
> call stubs or other linker generated code. I would be concerned about
> moving the build of the milli routines further back in the build
> sequence although it may work. Libgcc depends on the milli routines.
Most likely libgcc is still the correct time to build them. It's still
before any target applications are built if you're building a cross
toolchain, etc.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer