From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-11-23
Date: Fri, 25 Nov 2016 09:09:15 +0100 [thread overview]
Message-ID: <20161125090915.34071222@free-electrons.com> (raw)
In-Reply-To: <20161125002248.GA3200@tungsten.ozlabs.ibm.com>
Hello,
On Fri, 25 Nov 2016 11:22:48 +1100, Sam Bobroff wrote:
> > > powerpc64 | oprofile-1.1.0 | NOK | http://autobuild.buildroot.net/results/314446eb6824277187ce3e2a7285226d67f731f5
> >
> > checking for perfmon/pfmlib.h... no
> > configure: error: pfmlib.h not found; may be provided by libpfm devel or papi devel package
> >
> > Sam: we currently have:
> >
> > select BR2_PACKAGE_LIBPFM4 if BR2_powerpc
> > # libpfm4 is needed on PowerPC, and requires thread support
> > depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL || !BR2_powerpc
> >
> > Perhaps we need to also select libpfm4 on powerpc64 (and le) ?
>
> It looks like we do. I tried a build of oprofile on powerpc64le and
> it fails as above unless pfmlib is present. It will almost certainly
> be the same on powerpc64. Would you like me to send a patch?
Yes, please. Note that you also need to update the line:
depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL || !BR2_powerpc
Indeed: on PowerPC/PowerPC64 pfmlib is *required* and pfmlib needs NPTL
thread support, so we must have a BR2_TOOLCHAIN_HAS_THREADS_NPTL
dependency on PowerPC/PowerPC64, but not on other architectures. Since
this might be growing a bit long in terms of architectures to list, I
would suggest to introduce a hidden Config.in boolean:
# oprofile requires the libpfm4 dependency on a number of architectures
config BR2_PACKAGE_OPROFILE_NEEDS_LIBPFM4
config
default y if BR2_powerpc || BR2_powerpc64 || BR2_powerpc64le
(of course I have no idea if powerpc64le is supported, you would have
to check).
And then, in the BR2_PACKAGE_OPROFILE option, do something like:
select BR2_PACKAGE_LIBPFM4 if BR2_PACKAGE_OPROFILE_NEEDS_LIBPFM4
depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL || !BR2_PACKAGE_OPROFILE_NEEDS_LIBPFM4
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-25 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-23 Thomas Petazzoni
2016-11-24 8:44 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-11-24 15:26 ` Waldemar Brodkorb
2016-11-24 19:24 ` Jörg Krause
2016-11-24 19:58 ` Christian Stewart
2016-11-24 22:12 ` Jörg Krause
2016-11-25 0:22 ` Sam Bobroff
2016-11-25 8:09 ` Thomas Petazzoni [this message]
2016-11-25 10:47 ` Alexey Brodkin
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=20161125090915.34071222@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