From: Jeremy Huddleston <eradicator@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] broken (32bit) glibc ?
Date: Sat, 06 Aug 2005 09:33:14 -0700 [thread overview]
Message-ID: <1123345994.11655.1.camel@cloud.outersquare.org> (raw)
In-Reply-To: <1123237235.11188.36.camel@echelon.zagamma.vpn>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
On Fri, 2005-08-05 at 12:20 +0200, ViNiL 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?)
Yeah... uh... don't strip glibc. ;)
I'd recommend just grabbing glibc off of the 2005.1 livecd beta.
> 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
This is prolly 'cause your existing 32bit glibc is broke.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-08-06 16:34 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 ` [gentoo-amd64] " Ian Hastie
2005-08-06 9:37 ` ViNiL
2005-08-10 0:01 ` Ian Hastie
2005-08-06 16:33 ` Jeremy Huddleston [this message]
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=1123345994.11655.1.camel@cloud.outersquare.org \
--to=eradicator@gentoo.org \
--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