From: Richard Purdie <rpurdie@rpsys.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: elfutils - missing dependency on bzip2?
Date: Sun, 26 Feb 2012 23:24:58 +0000 [thread overview]
Message-ID: <1330298698.31855.27.camel@ted> (raw)
In-Reply-To: <CAGDS+nk2zxHM05n1rKzW8q-sgOmiMCVdwRP_LvWJ-B+1_8hH5Q@mail.gmail.com>
On Sun, 2012-02-26 at 09:25 -0800, Steve Sakoman wrote:
> After a pull this morning the rebuild if elfutils fails with:
>
> | /usr/bin/ld: cannot find -lbz2
> | collect2: ld returned 1 exit status
> | make[3]: *** [libdw.so] Error 1
> | make[3]: Leaving directory
> `/media/Work/yocto/tmp/work/i686-linux/elfutils-native-0.148-r5/elfutils-0.148/libdw'
>
> If I build bzip2-native and then rebuild elfutils-native all is well
> and the build continues until the next failure (mesa-dri-glsl-native,
> fwiw, haven't investigated that one yet).
This sounds like there might be a floating dependency in elfutils on
bzip2, if its present. We probably need to lock that down one way or
another.
> Anyone else see this, or is it just another case of my build machines
> being in a strange state?
I've seen mesa-dri-glsl-native myself and if its the same issue, this is
something the signature changes have highlighted. It was there before,
that change just exposed it.
Basically, the problem is compile running twice. You could do it before
with something like:
bitbake mesa-dri-glsl-native
bitbake mesa-dri-glsl-native -c compile -f
We either need to fix these makefile issues or run "make clean" against
them before rerunning make.
Cheers,
Richard
next prev parent reply other threads:[~2012-02-26 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 17:25 elfutils - missing dependency on bzip2? Steve Sakoman
2012-02-26 23:24 ` Richard Purdie [this message]
2012-02-27 0:34 ` Steve Sakoman
2012-02-27 6:30 ` Steve Sakoman
2012-02-27 6:38 ` Martin Jansa
2012-02-27 14:25 ` Steve Sakoman
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=1330298698.31855.27.camel@ted \
--to=rpurdie@rpsys.net \
--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.