Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linux-firmware: bump version and fix hash
Date: Thu, 1 Nov 2018 15:14:11 +0100	[thread overview]
Message-ID: <20181101141411.GU28575@scaer> (raw)
In-Reply-To: <CAK4VdL0_csVF1ZpA=J+V1J9o1v-1DRUNn9P6p7XymG_SEonn2A@mail.gmail.com>

Erico, All,

Adding Thomas in Cc, for he may need to act on existing patches ;-)

On 2018-10-28 08:59 +0100, Erico Nunes spake thusly:
[--SNIP--]
> Ok so I finally tested this out and it seems to be due to two reasons:
> 
> 1) The tar version in Fedora is 1.30, Buildroot host-tar is 1.29. I
> can reproduce it using 1.30, if I force a host-tar build before
> getting the source, it works.

I was pretty sure we had added support for download dependencies
recently, and added host-tar as needed, but it seems this series
of mine is still pending:

    https://patchwork.ozlabs.org/project/buildroot/list/?series=43275

> 2) This is a bit unsupported and I had already tried disabling it
> before reporting, but I was experimenting with system-side pigz
> (something like https://askubuntu.com/a/62608), this seems to affect
> it too.

So, we should now detect if gzip is acceptable for use by Buildroot, and
if it is not, build our own host-gzip.

Does pigz isdentifies itself as pigz, or does it really impersonate
gzip? If the former, then it will be easy to detect, but if the latter,
it becomes more complex (we'd have to compress a wellknown blob and see
if the compressed stream matches what we expect.)

> Maybe it is because I switched to testing with 'make source' rather
> than a full build to test it quickly?

Yes, see the series I referenced above, as well as its cover letter:
    http://lists.busybox.net/pipermail/buildroot/2018-May/221176.html

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-11-01 14:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 22:38 [Buildroot] [PATCH 1/1] linux-firmware: bump version and fix hash Erico Nunes
2018-09-27 18:50 ` Peter Korsgaard
2018-10-03 19:11   ` Erico Nunes
2018-10-03 19:40     ` Yann E. MORIN
2018-10-03 20:08       ` Bernd Kuhls
2018-10-28  7:59       ` Erico Nunes
2018-11-01 14:14         ` Yann E. MORIN [this message]
2018-11-01 21:06           ` Yann E. MORIN
2018-11-02 13:05             ` Erico Nunes

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=20181101141411.GU28575@scaer \
    --to=yann.morin.1998@free.fr \
    --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