From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: sudo build failure
Date: Wed, 20 Jul 2011 08:19:49 -0700 [thread overview]
Message-ID: <4E26F215.2020100@mentor.com> (raw)
In-Reply-To: <1311165760.30326.66.camel@phil-desktop>
On 07/20/2011 05:42 AM, Phil Blundell wrote:
> On Wed, 2011-07-20 at 07:16 -0500, Kumar Gala wrote:
>> Trying to build a powerpc64 target rootfs and I'm getting the following build failures on sudo. Wondering if anyone has seen anything similar:
>>
>> http://pastebin.com/MeqPn46Q
>
> There was a bug like that a few months ago which was caused by broken
> siteinfo files. Presumably your tree is fairly up to date, but it
> sounds like you have a similar kind of issue. You'll need to
> investigate why configure thinks you don't need -ldl.
And part of the problem, I suspect, is that we're still re-syncing
siteinfo stuff from oe.dev (where your file is based on) into oe-core
and oe.dev has a lot more stuff in common files (which I'm working on
bringing to oe-core right now).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-07-20 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 12:16 sudo build failure Kumar Gala
2011-07-20 12:42 ` Phil Blundell
2011-07-20 15:19 ` Tom Rini [this message]
2011-07-20 15:51 ` Kumar Gala
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=4E26F215.2020100@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@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.