Re: [gentoo-user] emerge -uD world dies: Unable to build
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 gcc tarball from an install cd, use emerge to unpack this as a binpkg. This gives you a probably less than optimum but working gcc, which can be used to build the desired gcc. Then unmerge the unpacked one. -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] emerge -uD world dies: Unable to build FIXED
--- 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 suggestions for this problem). Easy. Grab any old gcc tarball from an install cd, use emerge to unpack this as a binpkg. This gives you a probably less than optimum but working gcc, which can be used to build the desired gcc. Then unmerge the unpacked one. It wasn't gcc. See Volker's reply to leapfrogging versions Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] emerge -uD world dies: Unable to build
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
* IO-Socket-SSL-1.12.tar.gz RMD160 SHA1 SHA256 size
;-) ... [
ok ]
* checking ebuild checksums ;-) ...
[ ok
]
* checking auxfile checksums ;-) ...
[ ok
]
* checking miscfile checksums ;-) ...
[ ok
]
* checking IO-Socket-SSL-1.12.tar.gz ;-) ...
[ ok
]
Unpacking source...
Unpacking IO-Socket-SSL-1.12.tar.gz to
/var/tmp/portage/dev-perl/IO-Socket-SSL-1.12/work
Source unpacked.
Compiling source in
/var/tmp/portage/dev-perl/IO-Socket-SSL-1.12/work/IO-Socket-SSL-1.12
...
* Using ExtUtils::MakeMaker
You need the XS Version of Scalar::Util for dualvar()
support at Makefile.PL line 57.
*
* ERROR: dev-perl/IO-Socket-SSL-1.12 failed.
* Call stack:
*ebuild.sh, line 1701: Called
dyn_compile
*ebuild.sh, line 1039: Called qa_call
'src_compile'
*ebuild.sh, line 44: Called
src_compile
*ebuild.sh, line 1383: Called
perl-module_src_compile
* perl-module.eclass, line 147: Called
perl-module_src_prep
* perl-module.eclass, line 136: Called die
* The specific snippet of code:
* echo $pm_echovar | perl Makefile.PL
${myconf} INSTALLMAN3DIR='none'\
* PREFIX=/usr INSTALLDIRS=vendor
DESTDIR=${D} || die Unable to build! (are you using
USE=\build\?)
* The die message:
* Unable to build! (are you using USE=build?)
*
* If you need support, post the topmost build error,
and the call stack if relevant.
* A complete build log is located at
'/var/log/portage/dev-perl:IO-Socket-SSL-1.12:20080128-214330.log'.
*
* 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 old
gcc versions.
* Messages for package sys-libs/glibc-2.6.1:
* Generating all locales; edit /etc/locale.gen to
save time/space
* Messages for package dev-libs/xmlrpc-c-1.06.03:
* Neither CURL nor libwww support was selected
* No client library will be be built
* Messages for package app-admin/syslog-ng-2.0.6:
* It is highly recommended that app-admin/logrotate
be emerged to
* manage the log files. syslog-ng installs a file in
/etc/logrotate.d
* for logrotate to use.
* Messages for package sys-apps/xinetd-2.3.14:
*
* PLEASE NOTE: Everything is off by default with
access restricted to localhost.
*
* Messages for package
app-portage/gentoolkit-0.2.3-r1:
*
* Another alternative to qpkg and equery are the q
applets in
* app-portage/portage-utils
*
* The qpkg and etcat tools are deprecated in favor of
equery and
* are no longer installed in /usr/bin in this
release.
* They are still available in
/usr/share/doc/gentoolkit-0.2.3-r1/deprecated/
* if you *really* want to use them.
* Messages for package dev-perl/IO-Socket-SSL-1.12:
*
* ERROR: dev-perl/IO-Socket-SSL-1.12 failed.
* Call stack:
*ebuild.sh, line 1701: Called
dyn_compile
*ebuild.sh, line 1039: Called qa_call
'src_compile'
*ebuild.sh, line 44: Called
src_compile
*ebuild.sh, line 1383: Called
perl-module_src_compile
* perl-module.eclass, line 147: Called
perl-module_src_prep
* perl-module.eclass, line 136: Called die
* The specific snippet of code:
* echo $pm_echovar | perl Makefile.PL
${myconf} INSTALLMAN3DIR='none'\
* PREFIX=/usr INSTALLDIRS=vendor
DESTDIR=${D} || die Unable to build! (are you using
USE=\build\?)
* The die message:
* Unable to build! (are you using USE=build?)
*
* If you need support, post the topmost build error,
and the call stack if relevant.
* A complete build log is located at
'/var/log/portage/dev-perl:IO-Socket-SSL-1.12:20080128-214330.log'.
*
* Regenerating GNU info directory index...
* Processed 132 info files.
* IMPORTANT: 34 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
Maxim Wexler
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
--
gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] emerge -uD world dies: Unable to build
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 old gcc versions. Read this guide carefully and follow it to the letter: http://www.gentoo.org/doc/en/gcc-upgrading.xml -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] emerge -uD world dies: Unable to build
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 the version you want to uninstall): 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 ... --- !empty dir /etc/eselect --- !empty dir /etc/env.d/gcc --- !empty dir /etc/env.d --- !empty dir /etc * Running 'fix_libtool_files.sh 3.4.6' * Scanning libtool files for hardcoded gcc library paths... gcc-config error: Could not run/locate gcc :0: assertion failed: (gcc -dumpversion) | getline NEWVER) * Regenerating GNU info directory index... * Processed 0 info files. * IMPORTANT: 34 config files in '/etc' need updating. * See the CONFIGURATION FILES section of the emerge * man page to learn how to update config files. And now I don't seem to have any sort of gcc: localhost heathen # gcc --version gcc-config error: Could not run/locate gcc and emerge -uD world still fails at the same place. Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] emerge -uD world dies: Unable to build
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 Bothwick Top Oxymorons Number 7: Definite maybe signature.asc Description: PGP signature
Re: [gentoo-user] emerge -uD world dies: Unable to build
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: Called qa_call
'src_compile'
*ebuild.sh, line 44: Called
src_compile
*ebuild.sh, line 1383: Called
perl-module_src_compile
* perl-module.eclass, line 147: Called
perl-module_src_prep
* perl-module.eclass, line 136: Called die
* The specific snippet of code:
* echo $pm_echovar | perl Makefile.PL
${myconf} INSTALLMAN3DIR='none'\
* PREFIX=/usr INSTALLDIRS=vendor
DESTDIR=${D} || die Unable to build! (are you using
USE=\build\?)
* The die message:
* Unable to build! (are you using USE=build?)
-mw
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
--
gentoo-user@lists.gentoo.org mailing list
