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 07:52:01 -0300 [thread overview]
Message-ID: <51CEBC51.9030601@zacarias.com.ar> (raw)
In-Reply-To: <20130629104251.4697be00@skate>
On 06/29/2013 05:42 AM, Thomas Petazzoni wrote:
> I would prefer to see an explicit "depends on !" on the specific
> Blackfin external toolchains that are causing problems. If one day we
> get the internal backend to properly build a toolchain for Blackfin,
> then doing a "depends on !BR2_bfin" wouldn't make sense.
>
> The Blackin external toolchain versions aren't changing that often, so
> it shouldn't cause too much hassle to update dhpcd dependencies when
> that happens.
That would be all good and well if the internal toolchain worked, snip:
checking for F_SETLKW... yes
checking if mkdir takes one argument... no
This target does not support --with-cpu.
Valid --with options are:
make[1]: *** [configure-gcc] Error 1
make[1]: Leaving directory
`/home/gustavoz/b/fin/output/toolchain/gcc-4.7.3-initial'
make: ***
[/home/gustavoz/b/fin/output/toolchain/gcc-4.7.3-initial/.compiled] Error 2
(all defaults except +IPV6 for dhcpcd).
And 2012R1-RC2 fails to download properly (2012R2-RC2 too for that
matter but i've got a local copy).
I kind of doubt that 2012R1 being older has getifaddrs enabled though.
Regards.
next prev parent reply other threads:[~2013-06-29 10:52 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 [this message]
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
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=51CEBC51.9030601@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