From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] wireshark: new package
Date: Wed, 24 Oct 2012 17:06:29 +0200 [thread overview]
Message-ID: <20121024170629.40348273@skate> (raw)
In-Reply-To: <20121024144837.GA25255@sapphire.tkos.co.il>
Dear Baruch Siach,
On Wed, 24 Oct 2012 16:48:37 +0200, Baruch Siach wrote:
> Well, the ultimate solution would probably be to add a --disable-usr configure
> option, like the existing --disable-usr-local. I see if I can find time to
> work on this. I'm no autotools expert.
This really shouldn't be needed. No autotools-based package that I'm
aware of needs this. If the default include flags are not good, you
pass additional CFLAGS/CPPFLAGS, that's the way autoconf works.
So basically, the whole idea of adding /usr/include forcefully is
stupid and should be removed, IMO.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-10-24 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 14:13 [Buildroot] [PATCH v2] wireshark: new package Baruch Siach
2012-10-24 14:40 ` Thomas Petazzoni
2012-10-24 14:48 ` Baruch Siach
2012-10-24 15:06 ` Thomas Petazzoni [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=20121024170629.40348273@skate \
--to=thomas.petazzoni@free-electrons.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