public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nuitari <nuitari@melchior.nuitari.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Looks like I broke libc
Date: Fri, 4 Aug 2006 21:17:55 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0608042117040.12441@melchior.nuitari.net> (raw)
In-Reply-To: <44D3DD71.5030609@gmx.de>

>> Yay.  Somewhere in the course of normal compiling, I've managed to hork
>> something up.  I run a plain amd64 system, and usually don't do anything
>> funny outside of the stable packages unless I need to.  It appears I've
>> broken my glibc installation:
>>
>> configure:2289: checking for C compiler default output file name
>> configure:2292: gcc -march=athlon64 -O2 -pipe   conftest.c  >&5
>> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/../../../../x86_64-pc-linux-gnu/bin/ld:
>> skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
>> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/../../../../x86_64-pc-linux-gnu/bin/ld:
>> cannot find /lib/libc.so.6
>
> That sounds... bad ;) I cannot offer you any ideas on how that
> happened (did you check if /lib/libc.so.6 is present?), but I can
> offer you a quickpkg of my glibc:
> http://alcaline.gotdns.com/gentoo/glibc-2.3.6-r4.tbz2
>
> Hope that helps.

I had a similar problem once when I had x86 crossdev running. Removing it 
(and associated packages) and getting a quickpkg of glibc of a similar 
machine fixed it. The 32 bit version of libc got put at the same place 
then the 64 bit one.
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-08-05  1:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 19:06 [gentoo-amd64] Looks like I broke libc Michael Hordijk
2006-08-04 23:51 ` Michael Weyershäuser
2006-08-05  1:17   ` Nuitari [this message]
2006-08-05  1:18   ` [gentoo-amd64] " Michael Hordijk

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=Pine.LNX.4.64.0608042117040.12441@melchior.nuitari.net \
    --to=nuitari@melchior.nuitari.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