From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] libusb: disable on avr32
Date: Sun, 18 Nov 2012 15:43:17 +0200 [thread overview]
Message-ID: <20121118134316.GG25380@sapphire.tkos.co.il> (raw)
In-Reply-To: <CAHt8ZCMA8fQOQMu9QerQfA1Vye+WKaCo5MmQBEdDhdYjkBX--Q@mail.gmail.com>
Hi Simon,
On Sun, Nov 18, 2012 at 01:23:49PM +0000, Simon Dawson wrote:
> On 18 November 2012 13:12, Baruch Siach <baruch@tkos.co.il> wrote:
> >> > comment "ccid needs a toolchain with thread support"
> >> > - depends on !BR2_TOOLCHAIN_HAS_THREADS
> >> > + depends on !BR2_TOOLCHAIN_HAS_THREADS && !BR2_avr32
> >>
> >> Showing this comment when BR2_avr32 is enabled is not very helpful, IMHO,
> >> especially when the toolchain does have threads support.
> >
> > Replying to myself: was the intension here to say
> >
> > depends on !BR2_TOOLCHAIN_HAS_THREADS || !BR2_avr32
> >
> > ? Otherwise it doesn't make much sense either. Or am I missing something here?
>
> The ccid package is unavailable for avr32, and requires thread support
> in the toolchain. However, it is my understanding that current
> "policy" in Buildroot is not to display comments for packages that are
> not available for the currently-selected target architecture. That is
> why the thread-related comment is only visible if the target
> architecture is not avr32.
I see. Thanks for the explanation.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2012-11-18 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 12:59 [Buildroot] [PATCH v3] libusb: disable on avr32 spdawson at gmail.com
2012-11-18 13:08 ` Baruch Siach
2012-11-18 13:12 ` Baruch Siach
2012-11-18 13:23 ` Simon Dawson
2012-11-18 13:43 ` Baruch Siach [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=20121118134316.GG25380@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--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