From: Markus Niebel <list-09_ptxdist@tqsc.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] barebox: select host-lzop
Date: Fri, 13 Jun 2014 18:47:10 +0200 [thread overview]
Message-ID: <539B2B0E.8030401@tqsc.de> (raw)
In-Reply-To: <20140613062901.GG23595@pengutronix.de>
Am 13.06.2014 08:29, wrote Michael Olbrich:
> On Thu, May 15, 2014 at 04:19:21PM +0200, Markus Niebel wrote:
>> From: Markus Niebel <Markus.Niebel@tq-group.com>
>>
>> creation of barebox.z requires lzop. As this may be not installed,
>> let's handle this inside of our build logic.
>
> True, but that's not always built, right? The kernel has the same problem
> with the various compressions. I'd rather not built all tools that might be
> used.
>
I see. BTW I came over this because a costumers BSP faile to build due to not
installed lzop on the build machine and not built lzop in the BSP.
Mh - there is an option to select and build lzop under the linux menu - I must be blind.
Maybe it is helpful to have something similar for barebox (or to have a menu for
host tools under platform)
Markus
> Michael
>
>> Signed-off-by: Markus Niebel <Markus.Niebel@tq-group.com>
>> ---
>> platforms/barebox.in | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/platforms/barebox.in b/platforms/barebox.in
>> index 6e65f83..6f66d1f 100644
>> --- a/platforms/barebox.in
>> +++ b/platforms/barebox.in
>> @@ -10,6 +10,7 @@ config BAREBOX_ARCH_STRING
>> menuconfig BAREBOX
>> select BOOTLOADER
>> select HOST_LIBUSB if BAREBOX_NEEDS_HOST_LIBUSB
>> + select HOST_LZOP
>> prompt "barebox "
>> bool
>> help
>> --
>> 1.7.9.5
>>
>>
>> --
>> ptxdist mailing list
>> ptxdist@pengutronix.de
>>
>
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-06-13 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 14:19 Markus Niebel
2014-06-13 6:29 ` Michael Olbrich
2014-06-13 16:47 ` Markus Niebel [this message]
2014-06-23 13:37 ` Michael Olbrich
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=539B2B0E.8030401@tqsc.de \
--to=list-09_ptxdist@tqsc.de \
--cc=ptxdist@pengutronix.de \
/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