public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] emerge failed for sys-devel/binutils-2.23.2
@ 2014-01-11 22:16 Andrew Penhorwood
  2014-01-11 22:32 ` Tom Wijsman
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew Penhorwood @ 2014-01-11 22:16 UTC (permalink / raw
  To: gentoo-user

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

I tried to update my gentoo VM on Linode.com today.  I used "emerge --update 
--deep --with-bdeps=y @world" and sys-devel/binutils-2.23.2 was one of the items 
reported by portage.  Portage stated that the compile failed.  Here are the last 
few lines of the build.log.  Any help would be appreciated.

x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. 
-I/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2/gold 
-I/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2/gold 
-I/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2/gold/../include -I/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2/gold/../elfcpp 
-DLOCALEDIR="\"/usr/share/binutils-data/x86_64-pc-linux-gnu/2.23.2/locale\"" 
-DBINDIR="\"/usr/x86_64-pc-linux-gnu/binutils-bin/2.23.2\"" 
-DTOOLBINDIR="\"/usr/x86_64-pc-linux-gnu/bin\"" 
-DTOOLLIBDIR="\"/usr/x86_64-pc-linux-gnu/lib\""   -W -Wall    -D_
LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -frandom-seed=sparc.o -O2 -pipe -MT 
sparc.o -MD -MP -MF .deps/sparc.Tpo -c -o sparc.o /var/tmp/portage/sys-dev
el/binutils-2.23.2/work/binutils-2.23.2/gold/sparc.cc
{standard input}: Assembler messages:
{standard input}:86724: Warning: end of file not at end of a line; newline inserted
{standard input}:86987: Error: number of operands mismatch for `sub'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.gentoo.org/> for instructions.
make[4]: *** [output.o] Error 4
make[4]: *** Waiting for unfinished jobs....
mv -f .deps/symtab.Tpo .deps/symtab.Po
mv -f .deps/i386.Tpo .deps/i386.Po
mv -f .deps/main.Tpo .deps/main.Po
mv -f .deps/sparc.Tpo .deps/sparc.Po
mv -f .deps/x86_64.Tpo .deps/x86_64.Po
make[4]: Leaving directory 
`/var/tmp/portage/sys-devel/binutils-2.23.2/work/build/gold'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/var/tmp/portage/sys-devel/binutils-2.23.2/work/build/gold'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/var/tmp/portage/sys-devel/binutils-2.23.2/work/build/gold'
make[1]: *** [all-gold] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/binutils-2.23.2/work/build'
make: *** [all] Error 2
emake failed
  * ERROR: sys-devel/binutils-2.23.2::gentoo failed (compile phase):
  *   emake failed
  *
  * Call stack:
  *     ebuild.sh, line   93:  Called src_compile
  *   environment, line 2823:  Called toolchain-binutils_src_compile
  *   environment, line 3514:  Called die
  * The specific snippet of code:
  *       emake all || die "emake failed";
  *
  * If you need support, post the output of `emerge --info 
'=sys-devel/binutils-2.23.2::gentoo'`,
  * the complete build log and the output of `emerge -pqv 
'=sys-devel/binutils-2.23.2::gentoo'`.
  * The complete build log is located at 
'/var/tmp/portage/sys-devel/binutils-2.23.2/temp/build.log'.
  * The ebuild environment file is located at 
'/var/tmp/portage/sys-devel/binutils-2.23.2/temp/environment'.
  * Working directory: '/var/tmp/portage/sys-devel/binutils-2.23.2/work/build'
  * S: '/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2'

-- 
Andrew Penhorwood
ColdBits, LLC
www.coldbits.com
andrew@coldbits.com


[-- Attachment #2: Type: text/html, Size: 25316 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] emerge failed for sys-devel/binutils-2.23.2
  2014-01-11 22:16 [gentoo-user] emerge failed for sys-devel/binutils-2.23.2 Andrew Penhorwood
@ 2014-01-11 22:32 ` Tom Wijsman
  2014-01-11 23:19   ` [gentoo-user] " walt
  0 siblings, 1 reply; 6+ messages in thread
From: Tom Wijsman @ 2014-01-11 22:32 UTC (permalink / raw
  To: andrew; +Cc: gentoo-user

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

On Sat, 11 Jan 2014 17:16:36 -0500
Andrew Penhorwood <andrew@coldbits.com> wrote:

>   * ERROR: sys-devel/binutils-2.23.2::gentoo failed (compile phase):
>   *   emake failed
>   *
>   * Call stack:
>   *     ebuild.sh, line   93:  Called src_compile
>   *   environment, line 2823:  Called toolchain-binutils_src_compile
>   *   environment, line 3514:  Called die
>   * The specific snippet of code:
>   *       emake all || die "emake failed";
>   *
>   * If you need support, post the output of `emerge --info 
> '=sys-devel/binutils-2.23.2::gentoo'`,
>   * the complete build log and the output of `emerge -pqv 
> '=sys-devel/binutils-2.23.2::gentoo'`.
>   * The complete build log is located at 
> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/build.log'.
>   * The ebuild environment file is located at 
> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/environment'.
>   * Working directory:
> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/build'
>   * S:
> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2'

Can you please file a bug about this at https://bugs.gentoo.org and
attach all the requested information? At the very least comment with
the output of `emerge --info` and attach the complete build.log.

Thank you very much in advance.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: emerge failed for sys-devel/binutils-2.23.2
  2014-01-11 22:32 ` Tom Wijsman
@ 2014-01-11 23:19   ` walt
  2014-01-12  0:41     ` Andrew Penhorwood
  2014-01-12  3:30     ` Tom Wijsman
  0 siblings, 2 replies; 6+ messages in thread
From: walt @ 2014-01-11 23:19 UTC (permalink / raw
  To: gentoo-user

On 01/11/2014 02:32 PM, Tom Wijsman wrote:
> On Sat, 11 Jan 2014 17:16:36 -0500
> Andrew Penhorwood <andrew@coldbits.com> wrote:
> 
>>   * ERROR: sys-devel/binutils-2.23.2::gentoo failed (compile phase):
>>   *   emake failed
>>   *
>>   * Call stack:
>>   *     ebuild.sh, line   93:  Called src_compile
>>   *   environment, line 2823:  Called toolchain-binutils_src_compile
>>   *   environment, line 3514:  Called die
>>   * The specific snippet of code:
>>   *       emake all || die "emake failed";
>>   *
>>   * If you need support, post the output of `emerge --info 
>> '=sys-devel/binutils-2.23.2::gentoo'`,
>>   * the complete build log and the output of `emerge -pqv 
>> '=sys-devel/binutils-2.23.2::gentoo'`.
>>   * The complete build log is located at 
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/build.log'.
>>   * The ebuild environment file is located at 
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/environment'.
>>   * Working directory:
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/build'
>>   * S:
>> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2'
> 
> Can you please file a bug about this at https://bugs.gentoo.org and
> attach all the requested information? At the very least comment with
> the output of `emerge --info` and attach the complete build.log.

I was about to reply to Andrew that running an emerge with -j1 can make
the build log easier to scan for errors, and can sometimes even prevent
build errors in certain packages.

[OT]
Tom, I very rudely forgot to thank you for your reply to my recent post
about layman.  So...thank you!

As a group we tend to be tough on devs who actually answer questions here
even though we really are harmless.  No, really, we are, honest, just ask
us.


  



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: emerge failed for sys-devel/binutils-2.23.2
  2014-01-11 23:19   ` [gentoo-user] " walt
@ 2014-01-12  0:41     ` Andrew Penhorwood
  2014-01-12  3:36       ` Tom Wijsman
  2014-01-12  3:30     ` Tom Wijsman
  1 sibling, 1 reply; 6+ messages in thread
From: Andrew Penhorwood @ 2014-01-12  0:41 UTC (permalink / raw
  To: gentoo-user

I will try the -j1.  This is a VM that is initially setup my Linode.com.

Andrew

On 1/11/2014 6:19 PM, walt wrote:
> On 01/11/2014 02:32 PM, Tom Wijsman wrote:
>> On Sat, 11 Jan 2014 17:16:36 -0500
>> Andrew Penhorwood <andrew@coldbits.com> wrote:
>>
>>>    * ERROR: sys-devel/binutils-2.23.2::gentoo failed (compile phase):
>>>    *   emake failed
>>>    *
>>>    * Call stack:
>>>    *     ebuild.sh, line   93:  Called src_compile
>>>    *   environment, line 2823:  Called toolchain-binutils_src_compile
>>>    *   environment, line 3514:  Called die
>>>    * The specific snippet of code:
>>>    *       emake all || die "emake failed";
>>>    *
>>>    * If you need support, post the output of `emerge --info
>>> '=sys-devel/binutils-2.23.2::gentoo'`,
>>>    * the complete build log and the output of `emerge -pqv
>>> '=sys-devel/binutils-2.23.2::gentoo'`.
>>>    * The complete build log is located at
>>> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/build.log'.
>>>    * The ebuild environment file is located at
>>> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/environment'.
>>>    * Working directory:
>>> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/build'
>>>    * S:
>>> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2'
>> Can you please file a bug about this at https://bugs.gentoo.org and
>> attach all the requested information? At the very least comment with
>> the output of `emerge --info` and attach the complete build.log.
> I was about to reply to Andrew that running an emerge with -j1 can make
> the build log easier to scan for errors, and can sometimes even prevent
> build errors in certain packages.
>
> [OT]
> Tom, I very rudely forgot to thank you for your reply to my recent post
> about layman.  So...thank you!
>
> As a group we tend to be tough on devs who actually answer questions here
> even though we really are harmless.  No, really, we are, honest, just ask
> us.
>
>
>    
>
>
>


-- 
Andrew Penhorwood
ColdBits, LLC
www.coldbits.com
andrew@coldbits.com
740-358-9129



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: emerge failed for sys-devel/binutils-2.23.2
  2014-01-11 23:19   ` [gentoo-user] " walt
  2014-01-12  0:41     ` Andrew Penhorwood
@ 2014-01-12  3:30     ` Tom Wijsman
  1 sibling, 0 replies; 6+ messages in thread
From: Tom Wijsman @ 2014-01-12  3:30 UTC (permalink / raw
  To: w41ter; +Cc: gentoo-user

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

On Sat, 11 Jan 2014 15:19:23 -0800
walt <w41ter@gmail.com> wrote:

> On 01/11/2014 02:32 PM, Tom Wijsman wrote:
> > On Sat, 11 Jan 2014 17:16:36 -0500
> > Andrew Penhorwood <andrew@coldbits.com> wrote:
> > 
> >>   * ERROR: sys-devel/binutils-2.23.2::gentoo failed (compile
> >> phase):
> >>   *   emake failed
> >>   *
> >>   * Call stack:
> >>   *     ebuild.sh, line   93:  Called src_compile
> >>   *   environment, line 2823:  Called
> >> toolchain-binutils_src_compile
> >>   *   environment, line 3514:  Called die
> >>   * The specific snippet of code:
> >>   *       emake all || die "emake failed";
> >>   *
> >>   * If you need support, post the output of `emerge --info 
> >> '=sys-devel/binutils-2.23.2::gentoo'`,
> >>   * the complete build log and the output of `emerge -pqv 
> >> '=sys-devel/binutils-2.23.2::gentoo'`.
> >>   * The complete build log is located at 
> >> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/build.log'.
> >>   * The ebuild environment file is located at 
> >> '/var/tmp/portage/sys-devel/binutils-2.23.2/temp/environment'.
> >>   * Working directory:
> >> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/build'
> >>   * S:
> >> '/var/tmp/portage/sys-devel/binutils-2.23.2/work/binutils-2.23.2'
> > 
> > Can you please file a bug about this at https://bugs.gentoo.org and
> > attach all the requested information? At the very least comment with
> > the output of `emerge --info` and attach the complete build.log.
> 
> I was about to reply to Andrew that running an emerge with -j1 can
> make the build log easier to scan for errors, and can sometimes even
> prevent build errors in certain packages.

The errors are:

    {standard input}:86987: Error: number of operands mismatch for `sub'
    {standard input}: Error: open CFI at the end of file;
    missing .cfi_endproc directive

There is something wrong in the assembler code, a mismatch of of the
amounts of parameters passed to a 'sub' (subtract) instruction; then
it doesn't close some kind of CFI procedure towards the end of the
file, this then later causes the compiler to get killed:

    x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program
    cc1plus)

The other occasion is that the assembler code might be right, but then
there is something wrong with the system; I'll get back to that in my
other mail.

As a side note; -j1 bugs should still be filed such that we can
(temporarily) fix it for everyone in the ebuild, these can be
recognized by the amount of jobs mismatching in the build.log.

> [OT]
> Tom, I very rudely forgot to thank you for your reply to my recent
> post about layman.  So...thank you!
> 
> As a group we tend to be tough on devs who actually answer questions
> here even though we really are harmless.  No, really, we are, honest,
> just ask us.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: emerge failed for sys-devel/binutils-2.23.2
  2014-01-12  0:41     ` Andrew Penhorwood
@ 2014-01-12  3:36       ` Tom Wijsman
  0 siblings, 0 replies; 6+ messages in thread
From: Tom Wijsman @ 2014-01-12  3:36 UTC (permalink / raw
  To: andrew; +Cc: gentoo-user

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

On Sat, 11 Jan 2014 19:41:10 -0500
Andrew Penhorwood <andrew@coldbits.com> wrote:

> I will try the -j1.  This is a VM that is initially setup my
> Linode.com.

Advanced Vector Extensions (AVX) don't work on Linode, which is
what might cause the assembler instruction subtract to fail, as you
can see in my other mail; you can add -mno-avx at the end of your CFLAGS
in /etc/portage/make.conf to avoid the usage of AVX.

This is just a wild guess, but I've seen this helping other Linode
customers earlier that had similar problems; so, it might help you.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-01-12  3:37 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-11 22:16 [gentoo-user] emerge failed for sys-devel/binutils-2.23.2 Andrew Penhorwood
2014-01-11 22:32 ` Tom Wijsman
2014-01-11 23:19   ` [gentoo-user] " walt
2014-01-12  0:41     ` Andrew Penhorwood
2014-01-12  3:36       ` Tom Wijsman
2014-01-12  3:30     ` Tom Wijsman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox