From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libdrm: needs threads
Date: Mon, 21 Apr 2014 19:39:41 +0200 [thread overview]
Message-ID: <535557DD.5090407@openwide.fr> (raw)
In-Reply-To: <20140421173258.GG3359@free.fr>
Hi Yann,
Le 21/04/2014 19:32, Yann E. MORIN a ?crit :
> Romain, All,
>
> On 2014-04-21 19:28 +0200, Romain Naour spake thusly:
>> libdrm select libpthread-stubs that needs threads support.
>>
>> Fixes:
>> http://autobuild.buildroot.net/results/1da/1dad13110312a44b40b9ee4050b265de1f3c8a42/build-end.log
>>
>> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
>> ---
>> package/libdrm/Config.in | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/package/libdrm/Config.in b/package/libdrm/Config.in
>> index 72cf5f8..fdb541e 100644
>> --- a/package/libdrm/Config.in
>> +++ b/package/libdrm/Config.in
>> @@ -1,6 +1,7 @@
>> config BR2_PACKAGE_LIBDRM
>> bool "libdrm"
>> select BR2_PACKAGE_LIBPTHREAD_STUBS
>> + depends on BR2_TOOLCHAIN_HAS_THREADS # libpthread-stubs
>> depends on BR2_LARGEFILE
>> help
>> Direct Rendering Manager
>> @@ -59,5 +60,6 @@ endmenu
>>
>> endif
>>
>> -comment "libdrm needs a toolchain w/ largefile"
>> +comment "libdrm needs a toolchain w/ largefile, threads"
>> depends on !BR2_LARGEFILE
>> + depends on !BR2_TOOLCHAIN_HAS_THREADS
>
> This should be:
> depends on !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS
>
> Otherwise, the comment is only visible when both are not set, while we
> want to see the comment as soon as at least one is not set.
>
Thanks, I'll send a new patch.
Best regards,
Romain
prev parent reply other threads:[~2014-04-21 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 17:28 [Buildroot] [PATCH 1/1] libdrm: needs threads Romain Naour
2014-04-21 17:32 ` Yann E. MORIN
2014-04-21 17:39 ` Romain Naour [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=535557DD.5090407@openwide.fr \
--to=romain.naour@openwide.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.