From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why does boost require bzip2
Date: Mon, 03 Jun 2013 19:13:44 +0100 [thread overview]
Message-ID: <51ACDCD8.5080806@carallon.com> (raw)
Hello,
Does anyone know why the boost package requires bzip2? I am wanting to
build a very small rootfs and require only a single boost library, I
want to avoid the overhead of having the bzip2 library in my target fs.
If I change the boost package it still manages to build all the
libraries so I can't work out which libraries need bzip2. (I also have a
build failure when trying to build the boost context library, it is
failing because my arm target doesn't support the assembler, I'll look
into that error separately).
Thanks
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7471 9224
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2013-06-03 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 18:13 Will Wagner [this message]
2013-06-03 18:36 ` [Buildroot] Why does boost require bzip2 Peter Korsgaard
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=51ACDCD8.5080806@carallon.com \
--to=will_wagner@carallon.com \
--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