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 1681] New: Cross-compiled binaries should be installed into staging
Date: Tue,  4 May 2010 17:04:43 +0000 (UTC)	[thread overview]
Message-ID: <bug-1681-163@https.bugs.busybox.net/> (raw)

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

              Host: i686-linux
            Target: arm-softfloat-linux-uclibcgnueabi
           Summary: Cross-compiled binaries should be installed into
                    staging
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: gustavo at zacarias.com.ar
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 1633
  --> https://bugs.busybox.net/attachment.cgi?id=1633
Lua: don't install binaries into staging dir

Some packages install cross-compiled binaries into the staging dir.
This is wrong since they could predate host tools in the PATH and usually
aren't host-executable anyway.

-- 
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:[~2010-05-04 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 17:04 bugzilla at busybox.net [this message]
2010-05-04 17:04 ` [Buildroot] [Bug 1681] Cross-compiled binaries shouldn't be installed into staging bugzilla at busybox.net
2010-05-04 17:05 ` bugzilla at busybox.net
2010-05-04 18:02 ` bugzilla at busybox.net
2010-05-04 20:19 ` bugzilla at busybox.net
2010-07-29 19:31 ` bugzilla at busybox.net
2011-01-31 20:16 ` 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-1681-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