[gentoo-user] emerge -uD world dies: "Unable to build"

[gentoo-user] emerge -uD world dies: "Unable to build"

[maxim wexler]

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"

[Mick]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] emerge -uD world dies: "Unable to build"

[maxim wexler]

> 
> 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"

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] emerge -uD world dies: "Unable to build"

[maxim wexler]

> 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

Re: [gentoo-user] emerge -uD world dies: "Unable to build"

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

On Tuesday 29 January 2008, maxim wexler wrote:
> > 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)

Are you sure that you have emerged (successfully) the latest stable gcc?

> 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.

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).

If you are certain that you have had the correct gcc installed and gcc-config 
shows that it has been selected, and you have finished with the steps 
suggested in the guide above, then run revdep-rebuild -X -p -v once more for 
good measure before you try to emerge anything else.

HTH.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Chinese reader needed WAS emerge -uD world dies: "Unable to build"

[maxim wexler]

Hi group,


This gentoo user had a problem very similar to mine
but since the conversation is in Chinese I was unable
to determine the outcome. Maybe there's a clue in
there that will help me resolve my issue.

http://forums.gentoo.tw/viewtopic.php?p=57026&sid=a41bc0f35bf390cf14bf70eabc2512df


--- maxim wexler <blissfix@yahoo.com> wrote:

> 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
> 
> 



      ____________________________________________________________________________________
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] Chinese reader needed WAS emerge -uD world dies: "Unable to build"

[Willie Wong]

On Tue, Jan 29, 2008 at 07:13:15AM -0800, maxim wexler wrote:
> This gentoo user had a problem very similar to mine
> but since the conversation is in Chinese I was unable
> to determine the outcome. Maybe there's a clue in
> there that will help me resolve my issue.
> 
> http://forums.gentoo.tw/viewtopic.php?p=57026&sid=a41bc0f35bf390cf14bf70eabc2512df
> 

I don't know how relevant the post is to your problem. But the
solution that was found on the board is the following:

Noticing that the error says:

Errno architecture (x86_64-linux-2.6.16-gentoo-r7) does not match
executable architecture (x86_64-linux-2.6.20-gentoo-r9) at
/usr/lib64/perl5/site_perl/5.8.8/Errno.pm line 11

The poster went and edited line 11 in the offending file so the kernel
version matches the one he is running currently. Whether this is the
right thing to do I cannot comment on. 

W

-- 
Willie W. Wong                                      wwong@math.princeton.edu
408 Fine Hall,  Department of Mathematics,  Princeton University,  Princeton
A mathematician's reputation rests on the number of bad proofs he has given.
-- 
gentoo-user@lists.gentoo.org mailing list

Re: [gentoo-user] emerge -uD world dies: "Unable to build"

[Alan McKinnon]

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

[maxim wexler]

--- Alan McKinnon <alan.mckinnon@gmail.com> 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