From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Q7Ub2-0006wV-CV for garchives@archives.gentoo.org; Wed, 06 Apr 2011 15:24:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E2F671C15D; Wed, 6 Apr 2011 15:16:16 +0000 (UTC) Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 2E3101C156 for ; Wed, 6 Apr 2011 15:16:15 +0000 (UTC) Received: by ewy8 with SMTP id 8so565635ewy.40 for ; Wed, 06 Apr 2011 08:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=8NlzGY0c28c5uQqAdncEZjKezZDS3Zj1FsFSCYziW+Y=; b=obYsZ3KOY82rjJGupVpeuG0HN3Mu0yEqAtezTrYulRa01y/jjrLF5k3bxO2WjFFn0h 0+C+ohFb3+o6p9qj40n3lOP1XswyQwkzVSRKdz0n6tP0ygzRGOVw7pgkgn8GDLD144ro encj0G7ZNLq4rONbgHKJQiGGbWzoPqo98/PgU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=qHs+T7mUNlb1iKh9nVhsVa5bWjEyvNlkJf8aS3Yjse4b6ako4k0RDAzQZgobHrS/Zt bR49C/CN1hxAAX8f/ltz/4osJRdWNoqGpqRh2Zox+15YCNMS2mAD8u8YwA0Rpu5GkOVy YA4O2N1LNJjL0WSrJaJuks0GCprIFE6VjU5oo= Received: by 10.216.121.208 with SMTP id r58mr6476206weh.61.1302102975141; Wed, 06 Apr 2011 08:16:15 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.182.136 with HTTP; Wed, 6 Apr 2011 08:15:55 -0700 (PDT) In-Reply-To: References: <201104041341.14216.alan.mckinnon@gmail.com> <4D99BAD8.6030809@kutulu.org> <4D9B2A5E.7030600@kutulu.org> From: Gregory Fontenele Date: Wed, 6 Apr 2011 12:15:55 -0300 Message-ID: Subject: Re: [gentoo-user] Failed to emerge sys-devel/gcc-4.4.5 To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=00261883adfc4b68bd04a0417906 X-Archives-Salt: X-Archives-Hash: 8654f6d708801eaa0726dfc596313944 --00261883adfc4b68bd04a0417906 Content-Type: text/plain; charset=ISO-8859-1 want to leave this list but I can not, can someone erase me from this list? On Wed, Apr 6, 2011 at 02:55, Pandu Poluan wrote: > On Tue, Apr 5, 2011 at 21:42, Mike Edenfield wrote: > > On 4/5/2011 3:03 AM, Pandu Poluan wrote: > >> On Mon, Apr 4, 2011 at 19:34, Mike Edenfield wrote: > >>> On 4/4/2011 8:07 AM, Pandu Poluan wrote: > >>> > >>>> MAKEOPTS="-j3" > >>> > >>>> {standard input}: Assembler messages: > >>>> {standard input}:146362: Error: open CFI at the end of file; missing > >>>> .cfi_endproc directive > >>>> xgcc: Internal error: Killed (program cc1) > >>> > >>> This kind of error is often caused by the parallel make not quite > working. > >>> Try running the build like: > >>> > >>> MAKEOPTS="-j1" emerge =sys-devel/gcc-4.4.5 > >>> > >>> In general, whenever you get strange build errors (i.e. that have no > >>> immediately obvious cause) you should try again with MAKEOPTS="-j1". > Often > >>> it will fix the problem, but even when it doesn't you will usually get > a > >>> much more useful error. > >> > >> Thanks for the tip. Now it's 'partially successful': > >> > >> * QA Notice: Package has poor programming practices which may compile > >> * fine but exhibit random runtime failures. > > > > These aren't anything to worry about. > > > > Thanks for the explanation :-) > > >>>>> Installing (1 of 1) sys-devel/gcc-4.4.5 > >> * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.4.4' in > >> '/etc/env.d/gcc/' ! > >> * Running 'fix_libtool_files.sh 4.4.4' > >> * Scanning libtool files for hardcoded gcc library paths... > >> cat: ld.so.conf.d/*.conf: No such file or directory > >> gcc-config: error: could not run/locate 'gcc' > >> :0: assertion failed: (gcc -dumpversion) | getline NEWVER) > >> * Switching native-compiler to x86_64-pc-linux-gnu-4.4.5 ... > >> > >> * Your gcc has a bug with GCC_SPECS. > >> * Please re-emerge gcc. > >> * http://bugs.gentoo.org/68395 > > > > All of this is caused by your previous gcc profile being invalid, that > > is, pointing to a non-existent gcc version (one that had already been > > uninstalled). You *don't* have to re-emerge gcc as it says -- the bug is > > not in your GCC_SPECS but in gcc-config. > > > > You should first run gcc-config again to make sure your newly installed > > compiler it set as the default, then run `fix_libtool_files.sh 4.4.4` as > > the ebuild was trying to do. > > > > And you had to reply *after* gcc is re-emerged >.< > > Oh well, good to know, anyways... prevent more griefs in the future :-) > > > Rgds, > -- > Pandu E Poluan > ~ IT Optimizer ~ > Visit my Blog: http://pepoluan.posterous.com > > -- Atenciosamente, Gregory Fontenele --00261883adfc4b68bd04a0417906 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable want to lea= ve this list but I can not, can someone erase me from this list?
=
On Wed, Apr 6, 2011 at 02:55, Pandu Poluan <= span dir=3D"ltr"><pandu@poluan.info= > wrote:
On Tue, Apr 5, 20= 11 at 21:42, Mike Edenfield <kutulu= @kutulu.org> wrote:
> On 4/5/2011 3:03 AM, Pandu Poluan wrote:
>> On Mon, Apr 4, 2011 at 19:34, Mike Edenfield <kutulu@kutulu.org> wrote:
>>> On 4/4/2011 8:07 AM, Pandu Poluan wrote:
>>>
>>>> MAKEOPTS=3D"-j3"
>>>
>>>> {standard input}: Assembler messages:
>>>> {standard input}:146362: Error: open CFI at the end of fil= e; missing
>>>> .cfi_endproc directive
>>>> xgcc: Internal error: Killed (program cc1)
>>>
>>> This kind of error is often caused by the parallel make not qu= ite working.
>>> Try running the build like:
>>>
>>> MAKEOPTS=3D"-j1" emerge =3Dsys-devel/gcc-4.4.5
>>>
>>> In general, whenever you get strange build errors (i.e. that h= ave no
>>> immediately obvious cause) you should try again with MAKEOPTS= =3D"-j1". Often
>>> it will fix the problem, but even when it doesn't you will= usually get a
>>> much more useful error.
>>
>> Thanks for the tip. Now it's 'partially successful': >>
>> =A0* QA Notice: Package has poor programming practices which may c= ompile
>> =A0* =A0 =A0 =A0 =A0 =A0 =A0fine but exhibit random runtime failur= es.
>
> These aren't anything to worry about.
>

Thanks for the explanation :-)

>>>>> Installing (1 of 1) sys-devel/gcc-4.4.5
>> =A0* gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.4.4&#= 39; in
>> '/etc/env.d/gcc/' !
>> =A0* Running 'fix_libtool_files.sh 4.4.4'
>> =A0* Scanning libtool files for hardcoded gcc library paths...
>> cat: ld.so.conf.d/*.conf: No such file or directory
>> gcc-config: error: could not run/locate 'gcc'
>> :0: assertion failed: (gcc -dumpversion) | getline NEWVER)
>> =A0* Switching native-compiler to x86_64-pc-linux-gnu-4.4.5 ... >>
>> =A0* Your gcc has a bug with GCC_SPECS.
>> =A0* Please re-emerge gcc.
>> =A0* ht= tp://bugs.gentoo.org/68395
>
> All of this is caused by your previous gcc profile being invalid, that=
> is, pointing to a non-existent gcc version (one that had already been<= br> > uninstalled). You *don't* have to re-emerge gcc as it says -- the = bug is
> not in your GCC_SPECS but in gcc-config.
>
> You should first run gcc-config again to make sure your newly installe= d
> compiler it set as the default, then run `fix_libtool_files.sh 4.4.4` = as
> the ebuild was trying to do.
>

And you had to reply *after* gcc is re-emerged >.<

Oh well, good to know, anyways... prevent more griefs in the future :-)


Rgds,
--
Pandu E Poluan
~ IT Optimizer ~
Visit my Blog: = http://pepoluan.posterous.com




--
Atenciosamente,<= br>Gregory Fontenele
--00261883adfc4b68bd04a0417906--