From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9996] lz4 package does not install lz4 binaries in target
Date: Fri, 30 Jun 2017 09:25:04 +0000 [thread overview]
Message-ID: <bug-9996-163-d1ZqfzuKLM@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9996-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9996
Arnout Vandecappelle <arnout@mind.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|lz4 option does not install |lz4 package does not
|lz4 binaries in ramdisk |install lz4 binaries in
| |target
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
This was done by commit 8ad38a4fc2007df4bee9a941aed46c8771b6a84c by Gabe Evans.
It's a simple version bump, the commit message mentions nothing of this change:
package/lz4: bump version to r131
systemd v228 requires lz4 >= 125
Signed-off-by: Gabe Evans <gabe@hashrabbit.co>
[Thomas: only pass PREFIX=/usr at install time instead of using
LZ4_MAKE_OPTS, and also pass it for the host installation.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
So I guess it was an accident. Gabe, can you comment?
Jamin, could you send the patch (with a proper commit message and a
Signed-off-by) to the Buildroot mailing list so we can retain your authorship?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-06-30 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 22:06 [Buildroot] [Bug 9996] New: lz4 option does not install lz4 binaries in ramdisk bugzilla at busybox.net
2017-06-30 9:25 ` bugzilla at busybox.net [this message]
2018-01-10 22:41 ` [Buildroot] [Bug 9996] lz4 package does not install lz4 binaries in target bugzilla at busybox.net
2018-01-12 18:59 ` bugzilla at busybox.net
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=bug-9996-163-d1ZqfzuKLM@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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