Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 09:31:21 -0300	[thread overview]
Message-ID: <51CED399.8050408@zacarias.com.ar> (raw)
In-Reply-To: <20130629125530.412858a5@skate>

On 06/29/2013 07:55 AM, Thomas Petazzoni wrote:

>> (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.
> 
> Yes, one recent patch to the download infrastructure broke this. I
> should sent a different e-mail with this.

Downloaded manually and as i supposed, it lacks getifaddrs too.
Regards.

  reply	other threads:[~2013-06-29 12:31 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 [this message]
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=51CED399.8050408@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