public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: ViNiL <vinil@zagamma.cz>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] broken (32bit) glibc ?
Date: Sat, 06 Aug 2005 11:37:08 +0200	[thread overview]
Message-ID: <1123321028.11252.15.camel@echelon.zagamma.vpn> (raw)
In-Reply-To: <20050806025752.0958cb89@iahastie.local.net>

Duncan, thanks for your tips! I used my favourite trick: download stage2
+ tarball, chroot, quickpkg glibc, exit, emerge -avK glibc...

Ian Hastie wrote:
> 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.

This is it! /lib/ld-linux.so.2 pointed to /lib/ld-2.3.5.so which seemed
OK to me. When I changed it to /lib32/ld-linux.so.2, everything is
working fine, now.

The catch is: whenever I compile the glibc, the symlink is wrong again.
Don't you know why?


Thanks a lot.

My system is:
~amd64
glibc-2.3.5-r1
gcc-3.4.4
sandbox-1.2.11


ViNiL

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-08-06  9:38 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 [this message]
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=1123321028.11252.15.camel@echelon.zagamma.vpn \
    --to=vinil@zagamma.cz \
    --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