From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/lldpd: disable use of libbsd
Date: Thu, 18 Aug 2016 23:24:14 +0200 [thread overview]
Message-ID: <20160818232414.4a44b95f@free-electrons.com> (raw)
In-Reply-To: <1471554082-24303-1-git-send-email-yann.morin.1998@free.fr>
Hello,
On Thu, 18 Aug 2016 23:01:21 +0200, Yann E. MORIN wrote:
> libbsd installs at least one .pc file that contains a -isystem include
> path (-isystem /usr.include/bsd), but -isystem is not munged by
> pkg-config, so we end up using /usr/include/bsd which is not suitable
> for the target. And breaks big time (see failures, below).
>
> But using libbsd is completely optional. In fact, our lldpd.mk did not
> even express the dependency on libbsd, so we may well have had builds
> without libbsd.
>
> The functionality brought in by using libbsd is very minor (just setting
> the neighbour name in /proc/self/smdline), so we just make lldpd not use
> libbsd at all. There is no --disable-libbsd or such, so we just patch it
> out of configure.ac.
I don't like this fix, for two reasons:
* The patch is not upstreamable.
* It works around the problem, living a potentially problematic
libbsd.pc installed which can be used by other packages than lldpd.
Isn't the right solution to add support in pkg-config to mungle
-isystem flags?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-18 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 21:01 [Buildroot] [PATCH 1/2] package/lldpd: disable use of libbsd Yann E. MORIN
2016-08-18 21:01 ` [Buildroot] [PATCH 2/2] package/lldpd: explicit optional dependencies Yann E. MORIN
2016-08-18 21:25 ` Thomas Petazzoni
2016-08-18 21:24 ` Thomas Petazzoni [this message]
2016-08-24 0:55 ` [Buildroot] [PATCH 1/2] package/lldpd: disable use of libbsd Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2016-08-14 10:46 Yann E. MORIN
2016-08-14 20:26 ` Arnout Vandecappelle
2016-08-14 21:49 ` Yann E. MORIN
2016-08-15 21:54 ` Arnout Vandecappelle
2016-08-15 15:05 ` Vivien Didelot
2016-08-15 15:23 ` Yann E. MORIN
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=20160818232414.4a44b95f@free-electrons.com \
--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