From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package: add bcusdk
Date: Thu, 08 Nov 2012 12:05:59 +0100 [thread overview]
Message-ID: <509B9217.5040107@mind.be> (raw)
In-Reply-To: <509B8EF7.9090809@calao-systems.com>
On 11/08/12 11:52, Gr?gory Hermant wrote:
>>> >> + select BR2_PACKAGE_LIBPTHSEM
>> >
>> > ... and the architecture dependencies of libpthsem...
> Could you please enlighten me on this point ?
As I wrote in the review of libpthsem, pth doesn't work on a number
of the architectures we support. Since libpthsem is a fork of pth,
it's likely that it doesn't work in libpthsem either. Therefore, it
is likely that libpthsem requires some
depends on !BR2_microblaze && !BR2_...
which have to be inherited by the packages that select libpthsem.
(Thomas Petazzoni reported that pth doesn't work on arm-glibc, for
instance...).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-08 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 9:05 [Buildroot] [PATCH v2] package: add libpthsem Gregory Hermant
2012-11-06 9:05 ` [Buildroot] [PATCH v2] package: add bcusdk Gregory Hermant
2012-11-08 8:34 ` Arnout Vandecappelle
2012-11-08 10:52 ` Grégory Hermant
2012-11-08 11:05 ` Arnout Vandecappelle [this message]
2012-11-06 9:05 ` [Buildroot] [PATCH v2] package: add linknx Gregory Hermant
2012-11-07 21:51 ` [Buildroot] [PATCH v2] package: add libpthsem Arnout Vandecappelle
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=509B9217.5040107@mind.be \
--to=arnout@mind.be \
--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