This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Mon, Jul 17, 2000 at 05:59:22AM -0300, Alexandre Oliva wrote: > On Jul 14, 2000, Geoff Keating <geoffk@cygnus.com> wrote: > > > [aoliva said:] > > >> Despite the minor problem of how to bootstrap this situation. > > > You can have circular dependencies involving libc. > > Yup. I was talking about how to *create* the libraries in such a way > that each one uses the appropriate SONAME to refer to the other. As I > said, no big deal, it just has to be done carefully. > I am doing some experiments on the shared libgcc. I have added -Wl,--auxiliary,libgcc.so.3 when building my libc.so. I created a shell script, updatelibgcc. updatelibgcc takes CC and slibdir from environment to build/install libgcc.so.3. It seems to work so far. One interesting thing I noticed that libgcc.so might not be needed at all under Linux. I don't like the explicit dependency on libgcc.so. Can someone tell me if there is a case --auxiliary libgcc.so.3 is not enough for Linux? I may have missed something. Thanks. -- H.J. Lu (hjl@gnu.org)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |