Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
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 06:34:03 -0700	[thread overview]
Message-ID: <20090427133403.GD18788@smtp.west.cox.net> (raw)
In-Reply-To: <49F59B68.1010208@balister.org>

On Mon, Apr 27, 2009 at 07:47:52AM -0400, Philip Balister wrote:
> 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?

Any and all.

-- 
Tom Rini



  reply	other threads:[~2009-04-27 13:39 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 [this message]
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=20090427133403.GD18788@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox