From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dhcpcd: unavailable for bfin and fix another bug
Date: Sat, 29 Jun 2013 15:26:39 -0300 [thread overview]
Message-ID: <51CF26DF.20406@zacarias.com.ar> (raw)
In-Reply-To: <20130629143754.184edb41@skate>
On 06/29/2013 09:37 AM, Thomas Petazzoni wrote:
> Yes, of course it lacks getifaddrs, but I don't see how it changes the
> point I was making originally: it is not because /some/ external
> toolchains are affected that we should exclude an entire architecture
> from building a particular package.
Oh come on!
The ct-ng sample doesn't have UCLIBC_SUPPORT_AI_ADDRCONFIG set
(default=n in uClibc upstream).
None of Analog's toolchains have it either.
There's some old Ronetix blackfin toolchain that doesn't support it either.
So that just leaves a customized ct-ng or hand-built toolchain as a
canditate, which i take it as "very unlikely" to happen.
Regards.
prev parent reply other threads:[~2013-06-29 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 23:56 [Buildroot] [PATCH] dhcpcd: unavailable for bfin and fix another bug Gustavo Zacarias
2013-06-29 8:42 ` Thomas Petazzoni
2013-06-29 10:52 ` Gustavo Zacarias
2013-06-29 10:55 ` Thomas Petazzoni
2013-06-29 12:31 ` Gustavo Zacarias
2013-06-29 12:37 ` Thomas Petazzoni
2013-06-29 18:26 ` Gustavo Zacarias [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=51CF26DF.20406@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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