From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake: staging of binary over symlink breaks sysroot (lzma x xz)
Date: Wed, 28 Jul 2010 12:09:12 +0200 [thread overview]
Message-ID: <4C5001C8.4070607@gmail.com> (raw)
In-Reply-To: <1280309434.7083.8.camel@utx.lan>
Stanislav Brabec ha scritto, Il 28/07/2010 11:30:
> I just built an angstrom image and thinks failed.
>
> lzma image depends on lzma-native, grep and other programs that use .xz
> suffix for tarballs depend on xz-native.
> This fact itself is bad - it creates file conflicts in the sysroot.
>
> But things were even worse:
> - xz-native staged xz binary and lzma as a symlink to xz.
> - lzma-native tried to stage lzma 4 minutes later
>
> But staging of lzma apparently went wrong. Instead of removal of lzma
> symlink and installation of lzma binary, bitbake followed the symlink
> and staged lzma as xz with a result of broken build environment.
>
> I have bitbake-1.8.18.
>
Yes :-(
same here and other people I know are struggling trying to build.
/marco
next prev parent reply other threads:[~2010-07-28 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 9:30 bitbake: staging of binary over symlink breaks sysroot (lzma x xz) Stanislav Brabec
2010-07-28 9:52 ` Andrea Adami
2010-07-28 10:09 ` Marco Cavallini [this message]
2010-07-28 13:39 ` Marco Cavallini
2010-07-28 14:06 ` Bernhard Reutner-Fischer
2010-07-28 14:32 ` Bernhard Reutner-Fischer
2010-08-02 17:13 ` [PATCH, RFC]: automatically depend xz compressed URIs on xz-native [was: Re: bitbake: staging of binary over symlink breaks sysroot (lzma x xz)] Bernhard Reutner-Fischer
2010-08-02 17:49 ` Khem Raj
2010-08-02 18:07 ` Bernhard Reutner-Fischer
2010-08-02 18:13 ` Khem Raj
2010-08-02 18:20 ` Bernhard Reutner-Fischer
2010-08-02 20:23 ` Tom Rini
2010-08-04 10:37 ` [PATCH] base.bbclass: depend unpacking on native unpackers Bernhard Reutner-Fischer
2010-08-04 15:08 ` Khem Raj
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=4C5001C8.4070607@gmail.com \
--to=koansoftware@gmail.com \
--cc=openembedded-devel@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.