From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] legal-info: extract even no-redistribute packages
Date: Sat, 1 Mar 2014 14:36:37 +0100 [thread overview]
Message-ID: <20140301143637.440c054a@skate> (raw)
In-Reply-To: <1393605956-18133-1-git-send-email-yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Fri, 28 Feb 2014 17:45:56 +0100, Yann E. MORIN wrote:
> Fix this by always having legal-info extract the archives if one or
> more _LICENSE_FILES are specified.
>
> Fixes:
> http://autobuild.buildroot.net/results/884/884ba13bb024fd9a4818f3184495b2cccc3f595e/
> http://autobuild.buildroot.net/results/b6e/b6e152ce117764337c243a9f356b32064106f5c3/
> http://autobuild.buildroot.net/results/a58/a588b3b535a1259f7bc110a6323e5f33830bcd94/
> http://autobuild.buildroot.net/results/6d5/6d5da7fe5aee871d98fd5503875453556ccbf854/
> [...]
This patch is not actually fixing those build failures: they were
really caused by "make" not doing anything when no filesystem image
format was selected. Though the problem is real, and the patch
definitely valid.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-01 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 16:45 [Buildroot] [PATCH] legal-info: extract even no-redistribute packages Yann E. MORIN
2014-02-28 19:16 ` Thomas Petazzoni
2014-02-28 19:54 ` [Buildroot] Significant problem with the parallel build patch series Thomas Petazzoni
2014-02-28 19:58 ` Thomas Petazzoni
2014-02-28 23:39 ` [Buildroot] [PATCH] legal-info: extract even no-redistribute packages Fabio Porcedda
2014-03-01 13:19 ` Yann E. MORIN
2014-03-01 13:36 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-12 22:29 Yann E. MORIN
2014-03-13 11:52 ` Thomas De Schampheleire
2014-03-13 23:24 ` Luca Ceresoli
2014-03-14 21:40 ` 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=20140301143637.440c054a@skate \
--to=thomas.petazzoni@free-electrons.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