From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: elfutils build fails on Fedroa 14
Date: Tue, 21 Dec 2010 14:07:46 +0000 [thread overview]
Message-ID: <1292940466.25087.6094.camel@rex> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE9405051258@orsmsx504.amr.corp.intel.com>
On Thu, 2010-12-16 at 17:19 -0800, Kamble, Nitin A wrote:
> Thanks Josh for looking at this. Actually we closed this bug. It was
> issue with PATH variable for the bug reporter. It had . in the path
> too early, causing wrong ld to be chosen. Look at
> http://bugzilla.pokylinux.org/show_bug.cgi?id=572 for more
> information.
With issues like this which we can easily detect we should add then to
sanity.bbclass. I added a test in commit 68030f4.
Cheers,
Richard
prev parent reply other threads:[~2010-12-21 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 12:57 elfutils build fails on Fedroa 14 Wolfgang Denk
2010-12-11 10:47 ` Khem Raj
2010-12-15 16:26 ` Kamble, Nitin A
2010-12-15 16:44 ` Joshua Lock
2010-12-15 16:49 ` Joshua Lock
2010-12-17 1:19 ` Kamble, Nitin A
2010-12-17 3:31 ` Khem Raj
2010-12-21 14:07 ` Richard Purdie [this message]
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=1292940466.25087.6094.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=nitin.a.kamble@intel.com \
--cc=poky@yoctoproject.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