From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Can't Emerge gcc-4.7.3 on Multilib x86_64 Machine
Date: Wed, 3 Jul 2013 16:11:59 -0400 [thread overview]
Message-ID: <20130703201159.GP26738@ns1.bonedaddy.net> (raw)
I seem to have managed to fubar an amd64 multiboot machine I have as it fails
building gcc-4.7.3 and virtualbox.
Other amd64 machines are fine.
It looks like building anything with the -m 32 switch doesn't work
because ld doesn't like the libraries /lib/libc.so.6 and
/usr/lib/libc_nonshared.a.
I'm not sure why it's looking in those directories instead of /lib32 and
/usr/lib32 though since /lib is a symlink to /lib64 and /usr/lib is a
symlink to /usr/lib64.
The errors are the same:
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /lib/libc.so.6
when searching for /lib/libc.so.6
/usr/x86_64-pc-linux-gnu/bin/ld: cannot find /lib/libc.so.6
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible
/usr/lib/libc_nonshared.a when searching for /usr/lib/libc_nonshared.a
/usr/x86_64-pc-linux-gnu/bin/ld: cannot find /usr/lib/libc_nonshared.a
# gcc-config -l
[1] x86_64-pc-linux-gnu-4.7.3 *
#
Anyone seen this before?
Or have any suggestions?
Thanks,
Todd
reply other threads:[~2013-07-03 20:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130703201159.GP26738@ns1.bonedaddy.net \
--to=tsg@bonedaddy.net \
--cc=gentoo-user@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