From: felix@crowfix.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Where is this "GLIBCXX_3.4.9" coming from?
Date: Sat, 26 Jan 2008 23:14:22 -0800 [thread overview]
Message-ID: <20080127071422.GA13320@crowfix.com> (raw)
I can't upgrade coreutils because it complains like this:
>>> Unpacking coreutils-6.10.tar.lzma to /var/tmp/portage/sys-apps/coreutils-6.10-r1/work
lzma: /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by lzma)
tar: This does not look like a tar archive
tar: Error exit delayed from previous errors
ldd confirms something is fishy:
# ldd /usr/bin/lzma
/usr/bin/lzma: /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /usr/bin/lzma)
linux-gate.so.1 => (0xffffe000)
libstdc++.so.6 => /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6 (0xb7e6f000)
libm.so.6 => /lib/libm.so.6 (0xb7e49000)
libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1 (0xb7e3d000)
libc.so.6 => /lib/libc.so.6 (0xb7d08000)
/lib/ld-linux.so.2 (0xb7f97000)
But I don't have that version hanging around.
# gcc-config -l
[1] i686-pc-linux-gnu-4.1.2
[2] i686-pc-linux-gnu-4.2.2 *
I tried running
fix_libtool_files.sh 3.4.9
and it finds nothing to do.
I have remerged lxma-utils and get the same results.
I have several other packages with similar porblems, all related to
3.4.9. Where the heck is gcc getting the 3.4.9 nonsense from? Have I
missed some gcc upgrade step somewhere? Should I just demerge 4.1.2
and see what else breaks?
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
--
gentoo-user@lists.gentoo.org mailing list
reply other threads:[~2008-01-27 7:14 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=20080127071422.GA13320@crowfix.com \
--to=felix@crowfix.com \
--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