From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dhcpcd: unavailable for bfin and fix another bug
Date: Sat, 29 Jun 2013 10:42:51 +0200 [thread overview]
Message-ID: <20130629104251.4697be00@skate> (raw)
In-Reply-To: <1372463785-29537-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Fri, 28 Jun 2013 20:56:25 -0300, Gustavo Zacarias wrote:
> diff --git a/package/dhcpcd/Config.in b/package/dhcpcd/Config.in
> index a06a973..a032694 100644
> --- a/package/dhcpcd/Config.in
> +++ b/package/dhcpcd/Config.in
> @@ -1,5 +1,6 @@
> config BR2_PACKAGE_DHCPCD
> depends on BR2_INET_IPV6
> + depends on !BR2_bfin
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.
Best 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:[~2013-06-29 8:42 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 [this message]
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
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=20130629104251.4697be00@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