From: hjl@lucon.org (H.J. Lu)
To: law@cygnus.com
Cc: egcs@cygnus.com, libc-linux@gnu.org (GNU C Library)
Subject: Re: Patch for egcs 1.0.2
Date: Mon, 09 Feb 1998 11:31:00 -0000 [thread overview]
Message-ID: <m0y1wNv-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <5257.887009405@hurl.cygnus.com>
>
>
> In message < m0y0rK7-0004ecC@ocean.lucon.org >you write:
> > Hi,
> >
> > I'd like to see this in egcs 1.0.2. The reason for this is
> > glibc 2.1 is versioned and the dynamic linker needs to know
> > which version of libc the shared library is compiled against.
> >
> > Thanks.
> >
> >
> > --
> > H.J. Lu (hjl@gnu.org)
> > -
> > Sat Jan 10 14:03:43 1998 H.J. Lu (hjl@gnu.org)
> >
> > * config/linux.h (LIB_SPEC): Add -lc for -shared if
> > USE_GNULIBC_1 is not defined.
> > * config/sparc/linux.h; Ditto.
> >
> > * config/sparc/linux64.h (LIB_SPEC): Add -lc for -shared.
> >
> > * config/alpha/linux-elf.h (LIB_SPEC): New. Defined if
> > USE_GNULIBC_1 is not defined.
> HJ, these aren't even in the snapshots, and thus haven't been tested
> in any way shape or form by folks on the egcs list.
>
> As far as I know, this is the first time anyone on this list has
> ever seen these patches.
>
I forgot about it. I have used it for a while. But people who use
glibc 2.1 needs it. Otherwise, they will run into many problems.
BTW, it is from a glibc 2.1 bug report.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-02-09 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-06 9:12 H.J. Lu
1998-02-08 23:28 ` Jeffrey A Law
1998-02-09 11:31 ` H.J. Lu [this message]
1998-02-09 9:04 ` Jeffrey A Law
1998-02-09 9:08 ` H.J. Lu
1998-02-13 2:16 ` Jeffrey A Law
1998-02-14 15:56 ` H.J. Lu
1998-02-15 9:21 ` Jeffrey A Law
1998-02-15 12:08 ` H.J. Lu
1998-02-15 20:00 ` Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m0y1wNv-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=libc-linux@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).