From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4 of 4 RFC] Config.in files: unify comments of toolchain option dependencies
Date: Thu, 19 Sep 2013 16:54:45 +0200 [thread overview]
Message-ID: <20130919165445.72f8d5bb@skate> (raw)
In-Reply-To: <CAHXCMMK3NPuyfVeOfxAiJsC9ZCrBR56H9jFAQkrZZPmtp7A9xw@mail.gmail.com>
Dear Samuel Martin,
On Thu, 19 Sep 2013 13:47:55 +0200, Samuel Martin wrote:
> > comment "connman needs a toolchain with IPv6, WCHAR, threading and
> > resolver support"
> > depends on BR2_UCLIBC_VERSION_0_9_32 || \
> > !BR2_USE_WCHAR || !BR2_INET_IPV6 ||
> > !BR2_TOOLCHAIN_HAS_THREADS
> >
> >
> > I guess there must be some linke with uclibc 0.9.32, but does anyone
> > know more? Is this still correct?
> > In this patch I just took over the 'resolver' string, but it seems odd
> > anyway.
> >
> IIRC, this is about resolv.h, for which uclibc only provided stub (not full
> implementation) some years ago.
> I know there were patches implementing this on the web, but I don't know if
> they have been merged.
Well, if you look at the above condition, it seems to indicate that
0.9.33 is working fine to build connman.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-09-19 14:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 9:01 [Buildroot] [PATCH 0 of 4 RFC] Unification of comments on toolchain option dependencies Thomas De Schampheleire
2013-09-18 9:01 ` [Buildroot] [PATCH 1 of 4 RFC] trivial: manual: fix grammar of 'to express' Thomas De Schampheleire
2013-09-18 14:33 ` Peter Korsgaard
2013-09-18 9:01 ` [Buildroot] [PATCH 2 of 4 RFC] trivial: manual: multimedia is no longer a subdirectory Thomas De Schampheleire
2013-09-18 14:33 ` Peter Korsgaard
2013-09-18 9:01 ` [Buildroot] [PATCH 3 of 4 RFC] manual: add section about depending on toolchain options Thomas De Schampheleire
2013-09-18 11:15 ` Thomas De Schampheleire
2013-09-18 14:34 ` Peter Korsgaard
2013-09-18 16:34 ` Thomas Petazzoni
2013-09-18 17:30 ` Thomas De Schampheleire
2013-09-18 17:40 ` Thomas Petazzoni
2013-09-18 17:46 ` Gustavo Zacarias
2013-09-18 17:59 ` Thomas Petazzoni
2013-09-18 18:05 ` Gustavo Zacarias
2013-09-18 18:18 ` Thomas Petazzoni
2013-09-18 21:57 ` Arnout Vandecappelle
2013-09-19 4:10 ` Thomas Petazzoni
2013-09-19 19:06 ` Arnout Vandecappelle
2013-09-18 22:06 ` Arnout Vandecappelle
2013-09-19 7:23 ` Thomas De Schampheleire
2013-09-19 14:52 ` Thomas Petazzoni
2013-09-19 19:07 ` Arnout Vandecappelle
2013-09-18 9:01 ` [Buildroot] [PATCH 4 of 4 RFC] Config.in files: unify comments of toolchain option dependencies Thomas De Schampheleire
2013-09-19 10:57 ` Thomas De Schampheleire
2013-09-19 11:47 ` Samuel Martin
2013-09-19 14:54 ` Thomas Petazzoni [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=20130919165445.72f8d5bb@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 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.