From: Graham Murray <graham@gmurray.org.uk>
To: linux-gcc@vger.kernel.org, libc-alpha@sources.redhat.com
Subject: Re: glibc 2.3
Date: Sat, 05 Oct 2002 20:35:57 +0100 [thread overview]
Message-ID: <m3elb4fzky.fsf@home.gmurray.org.uk> (raw)
In-Reply-To: <3D9C1775.9030503@redhat.com> (Ulrich Drepper's message of "Thu, 03 Oct 2002 03:09:57 -0700")
Ulrich Drepper <drepper@redhat.com> writes:
> The 2.3.x release should be binary compatible with the 2.2 and earlier
> releases. All correct programs should continue to run.
I have encountered what looks like a binary incompatibility since
upgrading from 2.2.5.
I received the error message "relocation error: symbol
__libc_stack_end, version GLIBC_2.1 not defined in file ld-linux.so.2
with link time reference". This was on a program built from source
using the same gcc3.2 and glibc 2.2.5 (SuSE). Recompiling while
running glibc 2.3
next prev parent reply other threads:[~2002-10-05 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 10:09 glibc 2.3 Ulrich Drepper
2002-10-03 16:11 ` Mike Black
2002-10-03 16:22 ` Ulrich Drepper
2002-10-03 16:26 ` Mike Black
2002-10-03 16:33 ` Ulrich Drepper
2002-10-05 19:35 ` Graham Murray [this message]
2002-10-05 19:39 ` Jakub Jelinek
2002-10-15 15:57 ` Keld Jørn Simonsen
2002-10-15 17:41 ` Ulrich Drepper
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=m3elb4fzky.fsf@home.gmurray.org.uk \
--to=graham@gmurray.org.uk \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-gcc@vger.kernel.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 NNTP newsgroup(s).