From: Martin Costabel <costabel@wanadoo.fr>
To: Keith Jacob <kjacob@wantree.com.au>
Cc: linux-pmac list <linux-pmac@samba.anu.edu.au>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
linuxppc-user list <linuxppc-user@lists.linuxppc.org>
Subject: Re: undefined symbol: _IO_2_1_stdin_
Date: Sun, 20 Dec 1998 10:39:42 +0100 [thread overview]
Message-ID: <367CC5DE.D6035DDF@wanadoo.fr> (raw)
In-Reply-To: 199812200348.LAA24006@mule.wantree.com.au
Keith Jacob wrote:
>
> Any clues? Please?
>
> Full errror is
>
> error in loading shared libraries
> : undefined symbol: _IO_2_1_stdin_
>
> When?
>
> Whenever I try to run pre-compiled binaries (mostly from stock LinuxPPC
> RPMs) from late-1998 builds.
Are you trying to run R4.1 binaries with R4 libraries? This won't work.
You have to upgrade your glibc (and everything else). Better wait for R5
and stay with binaries linked with glibc-961212 (if you can find out
which ones they are :-)).
I am pretty sure this(*) will be one of the very FAQs over the next
months. That's why I kept the excessive crossposting list from Keith's
original. I would love to be wrong on this.
>
> BTW, Gary Thomas's latest egcs-1.1-1b RPMs include bins that exhibit this
> behaviour, e.g. gcc!
This is very strange. So maybe your problem is something else, after
all.
(*) A typical variant for pre-R5 binaries is:
error in loading shared libraries
: undefined symbol: __libc_start_main
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1998-12-20 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-20 3:45 undefined symbol: _IO_2_1_stdin_ Keith Jacob
1998-12-20 9:39 ` Martin Costabel [this message]
1998-12-20 11:05 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
1998-12-21 6:25 Keith Jacob
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=367CC5DE.D6035DDF@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=kjacob@wantree.com.au \
--cc=linux-pmac@samba.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.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).