Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-06-10
Date: Wed, 12 Jun 2019 09:06:47 +0200	[thread overview]
Message-ID: <20190612090647.388b2517@windsurf> (raw)
In-Reply-To: <20190612070200.GB6981@tungsten.ozlabs.ibm.com>

Hello,

On Wed, 12 Jun 2019 17:02:01 +1000
Sam Bobroff <sbobroff@linux.ibm.com> wrote:

> Ah, right. So that hack is no good, and it suggests that no hack on
> the buildroot side can work as long as GZIP is being overwritten by the
> package's build system. I'll have a go hacking the build system in cups
> to rename the GZIP variable but hopefully their upstream will fix it
> soon :-)
> 
> At least some of the compressed files are part of some kind of test data,
> so I'll see if they're the only ones and could perhaps be left out
> entirely.

Alternatively, Buildroot could use a gzip wrapper, installed in
$(HOST_DIR)/bin to pass this -n option when BR2_REPRODUCIBLE=y. The
gzip man page says that using the GZIP environment variable is
"obsolescent":

      The obsolescent environment variable GZIP can hold a set of default  options
       for  gzip.   These  options  are interpreted first and can be overwritten by
       explicit command line parameters.  As this can  cause  problems  when  using
       scripts,  this  feature  is  supported  only for options that are reasonably
       likely to not cause too much harm, and gzip warns if it is used.  This  fea?
       ture will be removed in a future release of gzip.

       You  can  use  an  alias  or script instead.  For example, if gzip is in the
       directory /usr/bin you can prepend $HOME/bin to your PATH and create an exe?
       cutable script $HOME/bin/gzip containing the following:

             #! /bin/sh
             export PATH=/usr/bin
             exec gzip -9 "$@"

Of course, if we go in this direction, we have to take care of what
happens if host-gzip is installed, as it would overwrite the wrapper.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-06-12  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-06-10 Thomas Petazzoni
2019-06-12  5:33 ` Sam Bobroff
2019-06-12  6:49   ` Thomas Petazzoni
2019-06-12  7:02     ` Sam Bobroff
2019-06-12  7:06       ` Thomas Petazzoni [this message]
2019-06-12  8:26         ` Arnout Vandecappelle
2019-06-12 10:04           ` Atharva Lele
2019-06-12 15:35           ` Yann E. MORIN

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=20190612090647.388b2517@windsurf \
    --to=thomas.petazzoni@bootlin.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