Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6722] New: Usage of $($(PKG)_DIR_PREFIX) is an issue with linux package
Date: Wed,  4 Dec 2013 20:32:35 +0000 (UTC)	[thread overview]
Message-ID: <bug-6722-163@https.bugs.busybox.net/> (raw)

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

           Summary: Usage of $($(PKG)_DIR_PREFIX) is an issue with linux
                    package
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: rjbarnet at rockwellcollins.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


The usage of the following:

$($(PKG)_DIR_PREFIX)/$(RAWNAME)

in package/pkg-generic could cause a potential issue with the linux package if
there were patches to ever be placed there. This is highly unlikely for the
linux package itself but if there was to be another package added to the top
level of BR and packages be applied, this could be an issue.

From build git source version 931b73e5eae4a3ba6b2e37db526fd7243a139e64, the
following are where $($(PKG)_DIR_PREFIX) is used.

$ grep -r \$\(\$\(PKG\)_DIR_PREFIX\) .
./package/dhrystone/dhrystone.mk:13
./package/pkg-generic.mk:92

I don't really know how to best fix this issue so this is more of an FYI.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-12-04 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 20:32 bugzilla at busybox.net [this message]
2013-12-04 20:55 ` [Buildroot] [Bug 6722] Usage of $($(PKG)_DIR_PREFIX) is an issue with linux package bugzilla at busybox.net
2013-12-05  7:31 ` bugzilla at busybox.net
2013-12-05  8:46 ` bugzilla at busybox.net
2013-12-05 14:43 ` bugzilla at busybox.net
2013-12-05 16:22 ` bugzilla at busybox.net
2013-12-05 16:28 ` bugzilla at busybox.net
2013-12-06 11:26 ` bugzilla at busybox.net
2013-12-06 11:58 ` bugzilla at busybox.net
2013-12-06 12:40 ` bugzilla at busybox.net
2013-12-06 12:46 ` bugzilla at busybox.net
2013-12-07 11:19 ` bugzilla at busybox.net
2013-12-07 20:11 ` bugzilla at busybox.net
2014-02-07  8:10 ` 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-6722-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox