From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gcc_4.2.4.bb: QA Issue: No GNU_HASH in theelf binary
Date: Wed, 29 Apr 2009 08:21:15 -0400 [thread overview]
Message-ID: <49F8463B.7040102@balister.org> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E3CF7A7@hiob.intern.dresearch.de>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Sledz, Steffen wrote:
>> I can confirm the failure in the default angstrom build for spitz from
>> the last week. Linking of gcc wrapper and few other utilities reported
>> the standard GNU_HASH QA error.
>>
>> Here is a possible fix or work-around. It's tested and it works, but
>> maybe it is not fully correct.
>>
>> It may be one of following problems. I did not search deeper which one
>> is true:
>> - Ignoring LDFLAGS passed to configure
>> - LDFLAGS x LDFLAGS_FOR_TARGET clash
>> - LDFLAGS_FOR_TARGET are not set in cross builds of native
>> gcc compiler
>> (i. e. not canadian)
>
> Fix works for me. But it would be nice if some members of the core team could ack it.
Does anyone see any downside for this patch? Have other people tested
it? I hate blind acking things.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-04-29 12:26 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
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 [this message]
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=49F8463B.7040102@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.