From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: gcc_4.2.4.bb: QA Issue: No GNU_HASH in the elf binary
Date: Mon, 27 Apr 2009 16:14:52 +0200 [thread overview]
Message-ID: <gt4ekt$ba2$1@ger.gmane.org> (raw)
In-Reply-To: <20090427134352.GE18788@smtp.west.cox.net>
On 27-04-09 15:43, Tom Rini wrote:
> On Mon, Apr 27, 2009 at 03:37:25PM +0200, Sledz, Steffen wrote:
>>>> At the moment we are not able to make a build out of the
>>>> .dev tree. :(
>>>
>>> For what machine and distro?
>>
>> hipox and angstrom
>>
>> But does this problem really depends on them? I thought it's a problem in the gcc-4.2.4 recipe.
>
> It's in all gcc versions, really.
No, it isn't:
NOTE: package gcc-4.3.3-r0: task do_build: completed
Anyway, isn't ldflags.patch supposed to fix missing ldflags?
regards,
Koen
next prev parent reply other threads:[~2009-04-27 14:20 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 [this message]
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='gt4ekt$ba2$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.