From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: qemu-native build regularly failing
Date: Tue, 20 Aug 2013 22:16:20 +0100 [thread overview]
Message-ID: <1507505.mjujvFaXNS@helios> (raw)
In-Reply-To: <CAF6bG8e=cCDyJGDNebVqaNSJ31PNYCUQ9xPNf_4p+mDVDUMbwA@mail.gmail.com>
On Tuesday 20 August 2013 23:26:44 Marko Lindqvist wrote:
> On 20 August 2013 16:32, Paul Eggleton <paul.eggleton@linux.intel.com>
> wrote:
> > On Tuesday 20 August 2013 15:51:21 Marko Lindqvist wrote:
> >> Build of qemu-native regularly fails with:
> >> | LINK sh4-softmmu/qemu-system-sh4
> >> |
> >> | /usr/lib/x86_64-linux-gnu/libXext.so.6: undefined reference to
> >>
> >> `_XEatDataWords'
> >>
> >> | collect2: error: ld returned 1 exit status
> >>
> >> This might be some dependency missing, as building first some packets
> >> (+ more importantly their dependencies) that do not depend on qemu and
> >> only then qemu dependant image success.
> >
> > Do you have something else causing libxext-native to be built by any
> > chance?
>
> Yes, it seems to be difference between the tree where build fails and
> the one where build success that former has no libxext-native built.
> Further, I tested just building libxext-native before building
> qemu-native, and then the build succeded.
The problem is we want qemu-native to be buildable both on systems without X11
and systems with X11, so the dependency has to be floating, and this is more or
less acceptable for a native recipe - there's only a problem when libxext-
native needs to be built. I can't see a lot of value in building libxext-
native in any case - what is causing it to be built on your system?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-20 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 12:51 qemu-native build regularly failing Marko Lindqvist
2013-08-20 13:32 ` Paul Eggleton
2013-08-20 20:26 ` Marko Lindqvist
2013-08-20 21:16 ` Paul Eggleton [this message]
2013-08-20 21:24 ` Otavio Salvador
2013-08-20 21:26 ` Paul Eggleton
2013-08-20 22:15 ` Marko Lindqvist
2013-08-21 16:33 ` Marko Lindqvist
2013-08-22 12:56 ` Marko Lindqvist
2013-08-22 13:03 ` Paul Eggleton
2013-08-22 14:27 ` Saul Wold
2013-08-30 2:25 ` Marko Lindqvist
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=1507505.mjujvFaXNS@helios \
--to=paul.eggleton@linux.intel.com \
--cc=cazfi74@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox