From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 531] New: let e2fsprogs package to export headers to staging dir if needed
Date: Sun, 2 Aug 2009 14:58:39 +0000 (UTC) [thread overview]
Message-ID: <bug-531-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=531
Host: Ubuntu 9.0.4 Server 32 Bit
Target: i686
Build: i686
Summary: let e2fsprogs package to export headers to staging dir
if needed
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: d.albano at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=563)
--> (https://bugs.busybox.net/attachment.cgi?id=563)
Let e2fsprogs headers to be copied in staging dir if needed
Hi,
as, specificed in bug #529, e2fsprogs package actually doesn't copy headers
into staging dir so util-linux doesn't compile complaining about missing
blkid/blkid/.h
The attached patch add support exporting only headers to staging dir
--
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:[~2009-08-02 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 14:58 bugzilla at busybox.net [this message]
2009-08-02 14:59 ` [Buildroot] [Bug 531] let e2fsprogs package to export headers to staging dir if needed bugzilla at busybox.net
2009-08-02 16:16 ` bugzilla at busybox.net
2009-08-31 8:07 ` bugzilla at busybox.net
2009-08-31 8:15 ` bugzilla at busybox.net
2010-02-21 18:51 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-07-19 7:16 ` bugzilla at busybox.net
2011-09-18 14:13 ` 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-531-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