mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Baeuerle, Florian" <Florian.Baeuerle@allegion.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v2 2/4] barebox: depend on HOST_LZOP
Date: Thu, 13 Dec 2018 13:02:50 +0000	[thread overview]
Message-ID: <fff69facea12cbb6c90f14d638ac81ffe26193a1.camel@allegion.com> (raw)
In-Reply-To: <20181213111628.ltbw6sbq3khvzxo3@pengutronix.de>

Am Donnerstag, den 13.12.2018, 12:16 +0100 schrieb Michael Olbrich:
> On Wed, Dec 12, 2018 at 02:52:54PM +0000, Baeuerle, Florian wrote:
> > The version shipped by ptxdist allows us to override the modification
> > time in the lzop headers.
> > 
> > Signed-off-by: Florian Bäuerle <florian.baeuerle@allegion.com>
> > ---
> >  platforms/barebox.in | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/platforms/barebox.in b/platforms/barebox.in
> > index 645366e93..46ab32a07 100644
> > --- a/platforms/barebox.in
> > +++ b/platforms/barebox.in
> > @@ -12,7 +12,7 @@ menuconfig BAREBOX
> >  	select HOST_LIBUSB if BAREBOX_NEEDS_HOST_LIBUSB
> >  	select HOST_OPENSSL if BAREBOX_NEEDS_HOST_OPENSSL
> >  	select HOST_IMX_CST if BAREBOX_NEEDS_HOST_IMX_CST
> > -	select HOST_LZOP if BAREBOX_NEEDS_HOST_LZOP
> > +	select HOST_LZOP if BAREBOX_NEEDS_HOST_LZOP ||
> > !SETUP_DISABLE_REPRODUCIBLE
> 
> This does not work. You will need to enable BAREBOX_NEEDS_HOST_LZOP
> manually if lzop is used by barebox.

Oops, you're right – in the platformconfig menu all SETUP_ symbols seem to be
undefined. Anyway, it's probably a bad idea to depend on regenerating a
platformconfig when the user en/disables user properties.

Can I just make barebox unconditionally depend on HOST_LZOP?

Other suggestions?


- Florian

> 
> Michael
> 
> >  	prompt "barebox                       "
> >  	bool
> >  	help
> > -- 
> > 2.19.2
> > 
> > _______________________________________________
> > ptxdist mailing list
> > ptxdist@pengutronix.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-12-13 13:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 14:52 [ptxdist] [PATCH v2 1/4] config/setup: make reproducible builds configurable Baeuerle, Florian
2018-12-12 14:52 ` [ptxdist] [PATCH v2 2/4] barebox: depend on HOST_LZOP Baeuerle, Florian
2018-12-13 11:16   ` Michael Olbrich
2018-12-13 13:02     ` Baeuerle, Florian [this message]
2018-12-13 13:34       ` Michael Olbrich
2018-12-14 11:54         ` Baeuerle, Florian
2018-12-12 14:52 ` [ptxdist] [PATCH v2 3/4] barebox: add support for reproducible build Baeuerle, Florian
2018-12-12 14:52 ` [ptxdist] [PATCH v2 4/4] barebox_mlo: " Baeuerle, Florian
2018-12-21 10:06 ` [ptxdist] [PATCH v3 1/3] config/setup: make reproducible builds configurable Baeuerle, Florian
2018-12-21 10:07   ` [ptxdist] [PATCH v3 2/3] barebox: add support for reproducible build Baeuerle, Florian
2018-12-21 10:07   ` [ptxdist] [PATCH v3 3/3] barebox_mlo: " Baeuerle, Florian
2019-02-08  9:33   ` [ptxdist] [PATCH v3 1/3] config/setup: make reproducible builds configurable Baeuerle, Florian
2019-02-08 13:48   ` 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=fff69facea12cbb6c90f14d638ac81ffe26193a1.camel@allegion.com \
    --to=florian.baeuerle@allegion.com \
    --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