From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [autobuild] package/oprofile: fix static linking
Date: Mon, 17 Aug 2015 22:29:02 +0200 [thread overview]
Message-ID: <20150817222902.31505c48@free-electrons.com> (raw)
In-Reply-To: <1439761598-18631-1-git-send-email-yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 16 Aug 2015 23:46:38 +0200, Yann E. MORIN wrote:
> When getext is enabled, popt links with -lintl, specifies it in its
> popt.pc and has done so for the past 6+ years. But oprofile does not
> use pkconfig to find popt, so misses -lintl, which is important for
> a static build. We have to do the call to pkgconfig manually...
>
> Fixes:
> http://autobuild.buildroot.org/results/a48/a485f2171a3fcbfa2e0e5aec8e653cf88512615d/
> http://autobuild.buildroot.org/results/b37/b374874f1915ab1d7aa6262604ccc8db102bb0b0/
> http://autobuild.buildroot.org/results/261/2616a63081ed8c55c7ca1a6879b1a6a14e19f918/
> http://autobuild.buildroot.org/results/73f/73f34ab59d54ded68ff60608a0212a6e5a5190e5/
> ...
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Baruch Siach <baruch@tkos.co.il>
>
> ---
> Change v2 -> v3:
> - don't make the call to pkgconfig contional (Baruch)
> - fix comment appropriately
Applied, thanks. Interestingly, oprofile's configure.ac checks for
pkg-config, but does not seem to use it...
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-17 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 21:46 [Buildroot] [PATCH] [autobuild] package/oprofile: fix static linking Yann E. MORIN
2015-08-17 20:29 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-16 13:37 Yann E. MORIN
2015-08-16 13:43 ` Baruch Siach
2015-08-16 14:51 ` 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=20150817222902.31505c48@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