All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9996] New: lz4 option does not install lz4 binaries in ramdisk
Date: Thu, 29 Jun 2017 22:06:39 +0000	[thread overview]
Message-ID: <bug-9996-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9996

            Bug ID: 9996
           Summary: lz4 option does not install lz4 binaries in ramdisk
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: jamin.collins at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Selecting the lz4 option in the menuconfig does not result in the lz4 binaries
being installed into the ramdisk, only the libraries.  This appears to be due
to a problem in the package's makefile.  The following change corrects this:

$ git diff
diff --git a/package/lz4/lz4.mk b/package/lz4/lz4.mk
index d350d4c09..4a7129998 100644
--- a/package/lz4/lz4.mk
+++ b/package/lz4/lz4.mk
@@ -37,7 +37,7 @@ endef

 define LZ4_INSTALL_TARGET_CMDS
        $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE)
DESTDIR=$(TARGET_DIR) \
-               PREFIX=/usr install -C $(@D)/lib
+               PREFIX=/usr install -C $(@D)
 endef

 $(eval $(generic-package))

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-06-29 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 22:06 bugzilla at busybox.net [this message]
2017-06-30  9:25 ` [Buildroot] [Bug 9996] lz4 package does not install lz4 binaries in target bugzilla at busybox.net
2018-01-10 22:41 ` 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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.