Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gcc_4.2.4.bb: QA Issue: No GNU_HASH in the elf binary
Date: Mon, 27 Apr 2009 07:47:52 -0400	[thread overview]
Message-ID: <49F59B68.1010208@balister.org> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E3CF78E@hiob.intern.dresearch.de>

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

Sledz, Steffen wrote:
> Ping.
> 
> At the moment we are not able to make a build out of the .dev tree. :(

For what machine and distro?

Philip




> 
>> -----Original Message-----
>> From: openembedded-devel-bounces@lists.openembedded.org 
>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On 
>> Behalf Of Sledz, Steffen
>> Sent: Friday, April 24, 2009 1:55 PM
>> To: openembedded-devel@lists.openembedded.org
>> Subject: [oe] gcc_4.2.4.bb: QA Issue: No GNU_HASH in the elf binary
>>
>> gcc_4.2.4.bb reports these errors for a few days. Can someone 
>> please have a look at it.
>>
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/gcc/usr/bin/arm-angstrom-linux-gnueabi-gcc'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/gcc/usr/libexec/gcc/arm-angstrom-linux-gnueab
>> i/4.2.4/collect2'
>> ERROR: QA Issue: non -dev package contains symlink .so: gcc 
>> path 
>> '/work/armv5te-angstrom-linux-gnueabi/gcc-4.2.4-r3/install/gcc
>> /usr/lib/gcc/arm-angstrom-linux-gnueabi/4.2.4/libgcc_s.so'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/g++/usr/bin/arm-angstrom-linux-gnueabi-g++'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/g++/usr/libexec/gcc/arm-angstrom-linux-gnueab
>> i/4.2.4/cc1plus'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/cpp/usr/bin/arm-angstrom-linux-gnueabi-cpp'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/cpp/usr/libexec/gcc/arm-angstrom-linux-gnueab
>> i/4.2.4/cc1'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/gfortran/usr/bin/arm-angstrom-linux-gnueabi-gfortran'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/gfortran/usr/libexec/gcc/arm-angstrom-linux-g
>> nueabi/4.2.4/f951'
>> ERROR: QA Issue: No GNU_HASH in the elf binary: 
>> '/home/sledz/oe/tmp.1/work/armv5te-angstrom-linux-gnueabi/gcc-
>> 4.2.4-r3/install/gcov/usr/bin/arm-angstrom-linux-gnueabi-gcov'
>> ERROR: QA run found fatal errors. Please consider fixing them.
>> ERROR: Error in executing: /opt/openembedded/recipes/gcc/gcc_4.2.4.bb
>> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
>> ERROR: Printing the environment of the function
>> ERROR: Error in executing: /opt/openembedded/recipes/gcc/gcc_4.2.4.bb
>> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
>> ERROR: Printing the environment of the function
>> ERROR: Error in executing: /opt/openembedded/recipes/gcc/gcc_4.2.4.bb
>> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
>> ERROR: Printing the environment of the function
>> ERROR: Error in executing: /opt/openembedded/recipes/gcc/gcc_4.2.4.bb
>> ERROR: Exception:<type 'exceptions.SystemExit'> Message:1
>> ERROR: Printing the environment of the function
>> ERROR: Build of /opt/openembedded/recipes/gcc/gcc_4.2.4.bb 
>> do_package failed
>> ERROR: Task 1281 (/opt/openembedded/recipes/gcc/gcc_4.2.4.bb, 
>> do_package) failed
>> ERROR: '/opt/openembedded/recipes/gcc/gcc_4.2.4.bb' failed
>>
>> Thx,
>> Steffen
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-04-27 11:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 11:55 gcc_4.2.4.bb: QA Issue: No GNU_HASH in the elf binary Sledz, Steffen
2009-04-27 11:07 ` Sledz, Steffen
2009-04-27 11:47   ` Philip Balister [this message]
2009-04-27 13:34     ` Tom Rini
2009-04-27 13:37     ` Sledz, Steffen
2009-04-27 13:43       ` Tom Rini
2009-04-27 14:14         ` Koen Kooi
2009-04-27 14:20           ` Tom Rini
2009-04-27 14:22           ` Sledz, Steffen
2009-04-28 19:13             ` [PATCH] " Stanislav Brabec
2009-04-29 11:04               ` [PATCH] gcc_4.2.4.bb: QA Issue: No GNU_HASH in theelf binary Sledz, Steffen
2009-04-29 12:21                 ` Philip Balister
2009-04-29 14:15                   ` Tom Rini
2009-04-29 16:26                     ` Stanislav Brabec
2009-04-29 16:45                       ` Tom Rini
2009-04-29 17:32                         ` Stanislav Brabec
2009-04-29 20:17                           ` Tom Rini
2009-04-29 20:21                             ` Tom Rini
2009-04-30 16:19                         ` Tom Rini
2009-04-30  5:19                       ` Tom Rini
2009-04-28 23:34           ` gcc_4.2.4.bb: QA Issue: No GNU_HASH in the elf binary Tom Rini
2009-04-27 14:10 ` Dmitry Eremin-Solenikov

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=49F59B68.1010208@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.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