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: David Edelsohn <dje at watson dot ibm dot com>
- To: law at redhat dot com
- Cc: Mark Mitchell <mark at codesourcery dot com>, John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>, "rth at redhat dot com" <rth at redhat dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 14 Feb 2002 14:48:29 -0500
- Subject: Re: Always link against static libgcc on hppa-linux
>>>>> law writes:
law> IMHO, hppa-linux should move the millicode routines into glibc or
law> libmilli (in which case all programs should link with libmilli).
I agree that these type of routines should be in the system C
library, not libgcc.a. The problem seems to be that the routines need to
be local requiring they be linked statically from an archive, not a shared
library. Glibc is a shared library, so I think it presents the same
problems as libgcc_s.so.
Given the way that shared libraries are arranged on SVR4 and
GNU/Linux, it seems that one needs to explicitly or implicitly add an
additional archive library to the link line because there is no way to
piggyback a static object into a shared library.
David