From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] libpcap: update static handling
Date: Mon, 24 Jan 2011 22:59:30 +0100 [thread overview]
Message-ID: <87tygyotdp.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201101241648.15991.vapier@gentoo.org> (Mike Frysinger's message of "Mon, 24 Jan 2011 16:48:15 -0500")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
>> LIBPCAP_INSTALL_STAGING_OPT = DYEXT=none DESTDIR="$(STAGING_DIR)" install
>> LIBPCAP_INSTALL_TARGET_OPT = DYEXT=none DESTDIR="$(TARGET_DIR)" install
Mike> yes, that would make it work, but that just makes me want to cry.
Mike> it makes a lot more sense imo to have $(PKG)_MAKE_OPT be passed
Mike> for all steps (and grepping the tree doesnt show any cases where
Mike> this would be a problem). if people still want a hook specific
Mike> to the build step, then it'd make sense to add $(PKG)_BUILD_OPT
Mike> or something similiar.
Yeah, similar to the recent patch to pass $PKG_MAKE_ENV for host
packages Thomas sent earlier today.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-24 21:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 3:10 [Buildroot] Pull request buildroot.git (vapier branch) Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 1/4] libpcap: update static handling Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 2/4] debugging: do not require no stripping Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 3/4] initial support for Blackfin processors Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 4/4] gdb: add support for Blackfin gdbserver Mike Frysinger
2011-01-23 10:17 ` [Buildroot] [PATCH 1/4] libpcap: update static handling Peter Korsgaard
2011-01-23 21:07 ` Mike Frysinger
2011-01-24 16:16 ` Thomas Petazzoni
2011-01-24 16:27 ` Peter Korsgaard
2011-01-24 21:48 ` Mike Frysinger
2011-01-24 21:59 ` Peter Korsgaard [this message]
2011-01-25 8:36 ` Thomas Petazzoni
2011-01-24 16:11 ` Thomas Petazzoni
2011-01-24 16:25 ` Peter Korsgaard
2011-01-24 21:46 ` Mike Frysinger
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=87tygyotdp.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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