Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] add option to enable AI_ADDRCONFIG support
Date: Thu, 15 Mar 2012 21:56:14 +0100	[thread overview]
Message-ID: <871uotshw1.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120315213337.448d1bfd@skate> (Thomas Petazzoni's message of "Thu, 15 Mar 2012 21:33:37 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> I believe it's a fairly small impact, but the problem is external uClibc
 >> toolchains (made by BR, ct-NG or elsewhere) which most likely won't have
 >> AI_ADDRCONFIG enabled, so mrouted (and gupnp) will fail at build time.

 Thomas> Is it common to have AI_ADDRCONFIG disabled in external toolchains?
 Thomas> Notice that we have a similar problem with ltp-testsuite at the moment.

Hard to say, but the config option defaults to 'n' in uClibc - So
chances are that it is.

 Thomas> Do we really want to add one more toolchain option just for
 Thomas> this small feature? Sounds like a big hammer, no?

True, but it is the safest approach. I don't feel strongly about it
though - Anybody?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-03-15 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 22:38 [Buildroot] add option to enable AI_ADDRCONFIG support Sven Neumann
2012-03-07 22:38 ` [Buildroot] [PATCH 1/2] toolchain: add option to enable AI_ADDRCONFIG support in uclibc Sven Neumann
2012-03-11 20:53   ` Peter Korsgaard
2012-03-07 22:38 ` [Buildroot] [PATCH 2/2] mrouted: select BR2_TOOLCHAIN_BUILDROOT_INET_ADDRCONFIG Sven Neumann
2012-03-08  8:17 ` [Buildroot] add option to enable AI_ADDRCONFIG support Thomas Petazzoni
2012-03-11 20:56   ` Peter Korsgaard
2012-03-15 20:33     ` Thomas Petazzoni
2012-03-15 20:56       ` Peter Korsgaard [this message]
2012-05-02 13:33         ` Gustavo Zacarias

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=871uotshw1.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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