On Tuesday 29 January 2008, Mick wrote:
Retrace your steps and follow the guide on this one. I'm sure that
you can recover if you ended up with no gcc, but don't know off hand
what it takes to do it. (I am sure that the forums are full of
suggestions for this problem).
Easy. Grab any old
--- Alan McKinnon [EMAIL PROTECTED] wrote:
On Tuesday 29 January 2008, Mick wrote:
Retrace your steps and follow the guide on this
one. I'm sure that
you can recover if you ended up with no gcc, but
don't know off hand
what it takes to do it. (I am sure that the
forums are full of
Hi group,
Would somebody look over the following and suggest a
fix?
I *did* try 'USE=build but got same error, same
place.
Emerging (24 of 235) dev-perl/IO-Socket-SSL-1.12 to
/
waiting for lock on
/usr/portage/distfiles/.locks/.IO-Socket-SSL-1.12.tar.gz.portage_lockfile
*
On Monday 28 January 2008, maxim wexler wrote:
Hi group,
Would somebody look over the following and suggest a
fix?
[snip...]
* Messages for package sys-devel/gcc-4.1.2:
* If you have issues with packages unable to locate
libstdc++.la,
* then try running 'fix_libtool_files.sh' on the
Read this guide carefully and follow it to the
letter:
http://www.gentoo.org/doc/en/gcc-upgrading.xml
deeper and deeper...
It is safe to remove the older GCC version at this
time. If you feel the need, please issue the following
command (as usual, substitute =sys-devel/gcc-3.4* with
On Mon, 28 Jan 2008 16:23:50 -0800 (PST), maxim wexler wrote:
gcc-4.1.2 was already emerged earlier but running gcc
--version reveals 3.4.6, so I ran
#emerge -aC =sys-devel/gcc-3.4.6-r2
gcc-config is set to use 3.4.6, which you have just removed. Run
gcc-config to fix this.
--
Neil
gcc-config is set to use 3.4.6, which you have just
removed. Run
gcc-config to fix this.
Done. But -uD world still barfs at the same place:
ERROR: dev-perl/IO-Socket-SSL-1.12 failed.
* Call stack:
*ebuild.sh, line 1701: Called
dyn_compile
*ebuild.sh, line 1039:
7 matches
Mail list logo
