From: maxim wexler <blissfix@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge -uD world dies: "Unable to build"
Date: Mon, 28 Jan 2008 17:52:24 -0800 (PST) [thread overview]
Message-ID: <417788.84878.qm@web31704.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080129004239.0231cce8@loonquawl.digimed.co.uk>
> 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
next prev parent reply other threads:[~2008-01-29 1:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 22:03 [gentoo-user] emerge -uD world dies: "Unable to build" maxim wexler
2008-01-28 22:25 ` Mick
2008-01-29 0:23 ` maxim wexler
2008-01-29 0:42 ` Neil Bothwick
2008-01-29 1:52 ` maxim wexler [this message]
2008-01-29 8:15 ` Mick
2008-01-29 21:50 ` Alan McKinnon
2008-01-29 22:27 ` [gentoo-user] emerge -uD world dies: "Unable to build" FIXED maxim wexler
2008-01-29 15:13 ` [gentoo-user] Chinese reader needed WAS emerge -uD world dies: "Unable to build" maxim wexler
2008-01-29 15:35 ` Willie Wong
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=417788.84878.qm@web31704.mail.mud.yahoo.com \
--to=blissfix@yahoo.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