From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/6] radvd: bump to version 1.9.1
Date: Mon, 23 Jul 2012 09:42:31 -0300 [thread overview]
Message-ID: <500D46B7.8060501@zacarias.com.ar> (raw)
In-Reply-To: <20120722210439.5b3c0dec@skate>
On 07/22/12 16:04, Thomas Petazzoni wrote:
> Le Sun, 15 Jul 2012 10:47:41 -0300,
> Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
>
>> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
>
> I don't know if it is related to this bump, but we have build failures
> on radvd since a few days. See
> http://autobuild.buildroot.org/results/48aabbc41dff2e4196dfd6e1e942cf6dbe050deb/build-end.log
> for example. Do you have the time to look into this?
>
> Thanks a lot!
>
> Thomas
Hi Thomas, sure.
Give the patch i'm sending a try, it should fix it since it's a wrong
Makefile dependency breaking highly-parallel builds. It doesn't seem to
break for me (4-core) but i can see how it could on other scenarios.
Not yet upstream until i get an OK (and subscribe to the radvd-devel ML
which seems slow for some reason).
Regards.
next prev parent reply other threads:[~2012-07-23 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 13:47 [Buildroot] [PATCH 1/6] mpfr: bump to version 3.1.1 Gustavo Zacarias
2012-07-15 13:47 ` [Buildroot] [PATCH 2/6] radvd: bump to version 1.9.1 Gustavo Zacarias
2012-07-22 19:04 ` Thomas Petazzoni
2012-07-23 12:42 ` Gustavo Zacarias [this message]
2012-07-15 13:47 ` [Buildroot] [PATCH 3/6] freetype: bump to version 2.4.10 Gustavo Zacarias
2012-07-15 13:47 ` [Buildroot] [PATCH 4/6] ipset: bump to version 6.13 Gustavo Zacarias
2012-07-15 13:47 ` [Buildroot] [PATCH 5/6] cifs-utils: bump to version 5.5 Gustavo Zacarias
2012-07-15 13:47 ` [Buildroot] [PATCH 6/6] grep: bump to version 2.13 Gustavo Zacarias
2012-07-15 20:20 ` [Buildroot] [PATCH 1/6] mpfr: bump to version 3.1.1 Thomas Petazzoni
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=500D46B7.8060501@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