Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J. Hammel <buildroot@graphics-muse.org>
To: buildroot@busybox.net
Subject: [Buildroot] connman requirement for resolver in toolchain
Date: Thu, 24 May 2012 09:10:51 -0600	[thread overview]
Message-ID: <1337872251.4288.13.camel@feynman.coloradoengineeringinc.com> (raw)
In-Reply-To: <20120517102649.6a6dc5ab@skate>

On Thu, 2012-05-17 at 10:26 +0200, Thomas Petazzoni wrote:
> If you are building your uClibc toolchain externally with Crosstool-NG,
> then it is up to you to adjust the uClibc configuration. You can either:
> 
>  *) Choose to make it identical to the uClibc configuration that
>     Buildroot uses for its internal backend, which gives you a good
>     certainty that packages will build
> 
>  *) Choose to progressively adjust your uClibc configuration to match
>     the particular requirements of the specific packages you're using.

I'm doing the latter.  I've diffed my uClibc config with the one for the
matching release in Buildroot and have enabled what I think is relevant
for resolver support, re: I configured uClibc with the resolver and nsl
stubs.  However, buildroot still doesn't allow me to configure connman.

I looked at connman's Config.in and it looks like this:

comment "connman needs a toolchain with resolver support"
    depends on !(BR2_UCLIBC_VERSION_SNAPSHOT ||
BR2_TOOLCHAIN_EXTERNAL_GLIBC || BR2_TOOLCHAIN_CTNG_eglibc ||
BR2_TOOLCHAIN_CTNG_eglibc

So if I'm using an external toolchain with uClibc it doesn't allow me to
configure connman, correct?  Is the uClibc resolver stub considered
unsufficient for use with connman?  Do I need to switch to glibc?

Also, it appears that BR2_TOOLCHAIN_CTNG_eglibc appears twice in that
dependency test.  Typo?

This is from the 2012.02 tarball release.  No patches.

Thanks.
-- 
Michael J. Hammel <buildroot@graphics-muse.org>

  parent reply	other threads:[~2012-05-24 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  3:01 [Buildroot] connman requirement for resolver in toolchain Michael J. Hammel
2012-05-17  8:26 ` Thomas Petazzoni
2012-05-18  4:38   ` Michael J. Hammel
2012-05-24 15:10   ` Michael J. Hammel [this message]
2012-05-24 17:42     ` Peter Korsgaard

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=1337872251.4288.13.camel@feynman.coloradoengineeringinc.com \
    --to=buildroot@graphics-muse.org \
    --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