From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Quick analysis of the last build failures
Date: Fri, 5 Apr 2013 14:22:49 +0200 [thread overview]
Message-ID: <20130405142249.4c97e61f@skate> (raw)
In-Reply-To: <CAG2jQ8iCYNPGcT=frmjx-zJtkFyKceCWi9csbEtj8BQk1_3Nqg@mail.gmail.com>
Dear Markos Chandras,
On Fri, 5 Apr 2013 13:17:54 +0100, Markos Chandras wrote:
> LTP will try to link to libcap if it is present, but until some time
> ago, libcap did not link against libattr which is required in order
> for
> these symbols to be exported. This was recently fixed in buildroot[1].
> So in order for this problem to go away, you need both libcap and attr
> in your buildroot config.
>
> http://git.buildroot.net/buildroot/commit/package/libcap/libcap.mk?id=1bf3d6f8cf3a2dca9ce1c6f3e68b077724f21db6
So, if I understand correctly, it should be something like:
ifeq ($(BR2_PACKAGE_LIBCAP),y)
LTP_TESTSUITE_DEPENDENCIES += libcap attr
endif
And in the Config.in:
select BR2_PACKAGE_ATTR if BR2_PACKAGE_LIBCAP
We would have two cases:
* libcap not enabled, it uses cap_set_file() from the C library.
Correct?
* libcap is enabled, we add the dependency on attr so that libcap
exposes cap_set_file().
Is this correct? Or is the dependency on libcap mandatory?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-05 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 12:12 [Buildroot] Quick analysis of the last build failures Thomas Petazzoni
2013-04-05 12:17 ` Markos Chandras
2013-04-05 12:22 ` Thomas Petazzoni [this message]
2013-04-05 12:36 ` Markos Chandras
2013-04-05 12:41 ` Thomas Petazzoni
2013-04-05 12:59 ` Gustavo Zacarias
2013-04-06 18:19 ` Samuel Martin
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=20130405142249.4c97e61f@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