From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1705] New: Fix pciutils broken cross compiling
Date: Thu, 6 May 2010 14:30:53 +0000 (UTC) [thread overview]
Message-ID: <bug-1705-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1705
Host: i686-linux
Target: powerpc-uclibc
Summary: Fix pciutils broken cross compiling
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
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 1663
--> https://bugs.busybox.net/attachment.cgi?id=1663
Fix pciutils broken cross compiling
The pciutils migration to gentargets broke cross compiling.
First problem is the internal install always trying to strip stuff, that's
wrong since native install doesn't know how to strip foreign binaries and also
breaks debugging since it's not conditional.
Second problem is the library isn't being cross compiled either (HOST variable
never set so it assumes native).
A third problem is the library never being installed and if the binaries link
against it (which they always do) they fail to work properly (make install-lib
needed).
Also added a comment about pci.ids / pci.ids.gz not being installed this time
around and being needed in the skeleton for a nice verbose lspci output.
This will be addressed post-2010.05 release with new infrastructure to fetch
files.
--
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.
next reply other threads:[~2010-05-06 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 14:30 bugzilla at busybox.net [this message]
2010-05-06 21:07 ` [Buildroot] [Bug 1705] Fix pciutils broken cross compiling 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-1705-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