From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/wireshark: Fix libpcap detection
Date: Tue, 29 Dec 2015 23:14:16 +0100 [thread overview]
Message-ID: <87h9j0dhs7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <566DDC20.5000104@mind.be> (Arnout Vandecappelle's message of "Sun, 13 Dec 2015 21:59:12 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> On 13-12-15 10:16, Bernd Kuhls wrote:
>> To reproduce the build error I had to install libpcap0.8-dev on my host
>> system, then wireshark configure picks up
>>
>> checking for pcap-config... /usr/bin/pcap-config
> To fundamentally avoid this type of issue (we have a bunch of fixes like this),
> I think we should add an additional directory that is put in the _beginning_ of
> the path in TARGET_MAKE_ENV. This directory could then be populated through the
> _CONFIG_SCRIPTS mechanism.
> What do the others think?
Sounds good to me!
> It will be a bit of work to revert all these fixes again :-)
But that can be done iteratively. The point is that buildroot will do
the right thing for these scripts out of the box (as long as they are
listed in the packages providing them) and users of those scripts will
automatically get the right ones.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2015-12-29 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 9:16 [Buildroot] [PATCH 1/2] package/wireshark: Fix libpcap detection Bernd Kuhls
2015-12-13 9:16 ` [Buildroot] [PATCH 2/2] package/wireshark: libpcap is an optional dependency Bernd Kuhls
2015-12-13 10:48 ` Gustavo Zacarias
2015-12-13 13:12 ` Thomas Petazzoni
2015-12-13 13:11 ` [Buildroot] [PATCH 1/2] package/wireshark: Fix libpcap detection Thomas Petazzoni
2015-12-13 20:59 ` Arnout Vandecappelle
2015-12-20 12:49 ` Yann E. MORIN
2015-12-20 15:49 ` Arnout Vandecappelle
2015-12-21 12:26 ` Yann E. MORIN
2015-12-29 22:14 ` Peter Korsgaard [this message]
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=87h9j0dhs7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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