From: Gary Thomas <gdt@linuxppc.org>
To: Keith Jacob <kjacob@wantree.com.au>
Cc: linuxppc-user list <linuxppc-user@lists.linuxppc.org>
Cc: linuxppc-user list <linuxppc-user@lists.linuxppc.org>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
linux-pmac list <linux-pmac@samba.anu.edu.au>
Subject: RE: undefined symbol: _IO_2_1_stdin_
Date: Sun, 20 Dec 1998 11:05:40 -0000 (GMT) [thread overview]
Message-ID: <XFMail.981220110540.gdt@linuxppc.org> (raw)
In-Reply-To: <199812200348.LAA24006@mule.wantree.com.au>
What libraries (GLIBC) do you have installed?
On 20-Dec-98 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.
>
> BTW, Gary Thomas's latest egcs-1.1-1b RPMs include bins that exhibit this
> behaviour, e.g. gcc!
>
> When I was using egcs-1.0-2e, and R4 packages there were no probs with
> bins I compiled myself.
>
------------------------------------------------------------------------
Gary Thomas |
email: gdt@linuxppc.org | "Fine wine is a necessity of
... opinions expressed here are mine | life for me"
and no one else would claim them! |
| Thomas Jefferson
------------------------------------------------------------------------
[[ 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 11:05 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
1998-12-20 11:05 ` Gary Thomas [this message]
-- 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=XFMail.981220110540.gdt@linuxppc.org \
--to=gdt@linuxppc.org \
--cc=kjacob@wantree.com.au \
--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).