From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] add option to enable AI_ADDRCONFIG support
Date: Thu, 15 Mar 2012 21:33:37 +0100 [thread overview]
Message-ID: <20120315213337.448d1bfd@skate> (raw)
In-Reply-To: <87wr6q26x5.fsf@macbook.be.48ers.dk>
Le Sun, 11 Mar 2012 21:56:22 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> 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.
Is it common to have AI_ADDRCONFIG disabled in external toolchains?
Notice that we have a similar problem with ltp-testsuite at the moment.
Do we really want to add one more toolchain option just for this small
feature? Sounds like a big hammer, no?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-15 20:33 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 [this message]
2012-03-15 20:56 ` Peter Korsgaard
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=20120315213337.448d1bfd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox