From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] boost 1.51.0 bz2 archive observations
Date: Sat, 01 Sep 2012 13:24:40 +0200 [thread overview]
Message-ID: <5041F078.2080106@mind.be> (raw)
In-Reply-To: <CAJkQPO=_T94Y854wErurMiwrQyZFbW7Mt9+9ak0xGDU0ahiEaw@mail.gmail.com>
On 08/31/12 17:39, Aras Vaichas wrote:
> Sorry for the cross-posting, but I'm not sure where to put this.
>
> There is a slight difference between the 1.51.0 and 1.50.0 boost bz2 files.
>
> e.g.
> \boost_1_50_0.tar.bz2\boost_1_50_0.tar\boost_1_50_0\
> \boost_1_51_0.tar.bz2\boost_1_51_0.tar\.\boost_1_51_0\
>
> I went looking for this because I updated the Boost version to 1.51.0
> in Buildroot and it failed to find the bootstrap.sh file because it
> wasn't in the expected directory.
This happens because buildroot uses the --strip-components=1 option of
tar to remove the leading path component - and now this is just the '.' that
is removed.
If the boost maintainers could repackage the tar file without the leading .,
that would be really nice for us. If not, we have to construct a workaround
in buildroot to treat the boost extraction specially. (Aras: you can probably
just add "/boost_1_51_0" to all the references to $(@D) in the .mk file.)
>
> e.g.
> /opt/br/output/build$ find -name "bootstrap.sh"
> ./boost-1.51.0/boost_1_51_0/tools/build/v2/bootstrap.sh
> ./boost-1.51.0/boost_1_51_0/bootstrap.sh
> ./boost-1.50.0/tools/build/v2/bootstrap.sh
> ./boost-1.50.0/bootstrap.sh
>
> Buildroot fails to find the boostrap.sh file and the build fails.
>
> When I tried to untar it manually I got an error.
>
> $ tar xjf boost_1_51_0.tar.bz2
> tar: .: Cannot utime: Operation not permitted
> tar: .: Cannot change mode to rwxr-xr-t: Operation not permitted
> tar: Exiting with failure status due to previous errors
This you can ignore: you're extracting in /tmp which isn't owned by
you, so you can't change the metadata of /tmp. All files are still
untarred, it's just the exit code that's not 0.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-09-01 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 15:39 [Buildroot] boost 1.51.0 bz2 archive observations Aras Vaichas
2012-09-01 11:24 ` Arnout Vandecappelle [this message]
2012-09-01 11:45 ` Samuel Martin
2012-09-01 11:49 ` Arnout Vandecappelle
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=5041F078.2080106@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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