Am Mittwoch, 14. Mai 2008 schrieb ext [EMAIL PROTECTED]:
So I moved 05compiler out of the way (I want to preserve that time
stamp just in case I do need to restore it), ran env-update again, and
now lzma is happy. I can run man again! Things which failed emerge
now build -- 323 to go.
Another way (simple) to resolve the issue is to re-emerge lzma-utils with
nocxx flag
Sylvain Chouleur
Date: Wed, 14 May 2008 11:28:10 -0700
From: [EMAIL PROTECTED]
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why does my system still want gcc 3.4.9?
On Wed, May 14, 2008
Am Donnerstag, 15. Mai 2008 schrieb ext Sylvain Chouleur:
Another way (simple) to resolve the issue is to re-emerge lzma-utils with
nocxx flag
No. It's just a workaround that works with certain packages, but fails for
others (where C++ is not optional). The solution is to fix the broken
On Thu, May 15, 2008 at 10:31:09AM +0200, Dirk Heinrichs wrote:
Am Donnerstag, 15. Mai 2008 schrieb ext Sylvain Chouleur:
Another way (simple) to resolve the issue is to re-emerge lzma-utils with
nocxx flag
No. It's just a workaround that works with certain packages, but fails for
others
Am Mittwoch, 14. Mai 2008 schrieb ext [EMAIL PROTECTED]:
The short of it is that a lot of binaries on my system are linked
against gcc 3.4.9, even if I remerge them from scratch.
There is no such thing as gcc 3.4.9.
It happened
with gcc 4.2.2, I emerged 4.2.3 and it still happens. The
On Mittwoch, 14. Mai 2008, [EMAIL PROTECTED] wrote:
I have been battling this weirdness for several months, and it has
been getting worse and worse. Now I can't even unpack half the man
pages.
The short of it is that a lot of binaries on my system are linked
against gcc 3.4.9, even if I
On Wed, May 14, 2008 at 08:19:38AM +0200, Dirk Heinrichs wrote:
There is no such thing as gcc 3.4.9.
You emerged it with 4.2.3, but _at_runtime_ it's trying to get libstdc++
from 4.1.2. Check your environment, especially all variables with PATH in
their name (env|grep PATH), as well as
Am Mittwoch, 14. Mai 2008 schrieb [EMAIL PROTECTED]:
Try: LD_LIBRARY_PATH=/usr/lib/gcc/i686-pc-linux-gnu/4.2.3 ldd
/usr/bin/lzma
This works.
Good.
If this works, try running env-update source /etc/profile, then
just ldd /usr/bin/lzma again.
Unfortunately, this doesn't work.
Did
On Wed, May 14, 2008 at 06:40:24PM +0200, Dirk Heinrichs wrote:
Did you check /etc/ld.so.conf, maybe 4.1.2 is still listed before 4.2.3?
You may also need to clean up /etc/env.d a bit and running gcc-config again
afterwards also seems to be a good idea.
Thanks. I started looking at it
I have been battling this weirdness for several months, and it has
been getting worse and worse. Now I can't even unpack half the man
pages.
The short of it is that a lot of binaries on my system are linked
against gcc 3.4.9, even if I remerge them from scratch. It happened
with gcc 4.2.2, I
10 matches
Mail list logo
