From: Ian Hastie <ianh@iahastie.clara.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] broken (32bit) glibc ?
Date: Sat, 6 Aug 2005 02:57:52 +0100 [thread overview]
Message-ID: <20050806025752.0958cb89@iahastie.local.net> (raw)
In-Reply-To: <1123237235.11188.36.camel@echelon.zagamma.vpn>
On Fri, 05 Aug 2005 12:20:35 +0200
ViNiL <vinil@zagamma.cz> wrote:
> Hello!
>
> After upgrading glibc to 2.3.5-r1, I am no longer able to run 32bit
> binaries. The error is: "Accessing a corrupted shared library" I guess
> the 32bit linker is broken (is it ok if this file is stripped?)
>
> What's more. I cannot compile any other glibc, now. It ends with:
> configure: error: cannot compute sizeof (long double), 77
> ./conftest: Accessing a corrupted shared library
>
> I have 32bit emul enabled in kernel.
>
> Any advice?
This sounds like a problem that I had once with an early glibc-2.3.5.
It was that the soft link at /lib/ld-linux.so.2 was set wrongly.
Firstly this is what you should get.
# ls -l /lib/ld-linux.so.2
lrwxrwxrwx 1 root root 22 Jul 25 01:11 /lib/ld-linux.so.2 ->
../lib32/ld-linux.so.2
If you don't then just do this
# rm /lib/ld-linux.so.2
# ln -s ../lib32/ld-linux.so.2 /lib/ld-linux.so.2
# ldconfig
That should fix the problem.
--
Ian.
EOM
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-06 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 10:20 [gentoo-amd64] broken (32bit) glibc ? ViNiL
2005-08-05 11:17 ` [gentoo-amd64] " Duncan
2005-08-06 13:23 ` [gentoo-amd64] gcc-4.0.1 compiled glibc-2.3.5.20050722, SUCCESS! Was: " Duncan
2005-08-06 16:43 ` Jeremy Huddleston
2005-08-06 19:12 ` [gentoo-amd64] " Duncan
2005-08-06 21:01 ` Jeremy Huddleston
2005-08-07 13:23 ` [gentoo-amd64] " Duncan
2005-08-06 1:57 ` Ian Hastie [this message]
2005-08-06 9:37 ` [gentoo-amd64] " ViNiL
2005-08-10 0:01 ` Ian Hastie
2005-08-06 16:33 ` Jeremy Huddleston
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=20050806025752.0958cb89@iahastie.local.net \
--to=ianh@iahastie.clara.net \
--cc=gentoo-amd64@lists.gentoo.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