All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bind: fix intermittent build issues with high BR2_JLEVEL
Date: Thu, 5 Nov 2015 22:42:03 +0100	[thread overview]
Message-ID: <20151105224203.77337e4b@free-electrons.com> (raw)
In-Reply-To: <1446721054-15603-1-git-send-email-heyleke@gmail.com>

Dear Jan Heylen,

Thanks for your patch!

On Thu,  5 Nov 2015 11:57:34 +0100, Jan Heylen wrote:
> From: Peter Korsgaard <jacmet@sunsite.dk>

I am not sure it is appropriate to send a patch in the name of someone
else. Maybe you're taking one of Peter's previous commit, and
re-applying it, but the context is different, so I believe it should be
under your own name.

> 
> Build sometimes breaks with:
> 
> libtool: link: `unix/os.lo' is not a valid libtool object
> make[3]: *** [rndc-confgen] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[4]: Leaving directory `/scratch/peko/build/bind-9.6-ESV-R4/bin/rndc/unix'
> 
> So disable parallel builds.

I've been trying to reproduce the parallel build issue, and I haven't
been able to do so. It seems our autobuilders also didn't catch it.

How often are you able to reproduce it ? On what type of build machine ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-11-05 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 10:57 [Buildroot] [PATCH] bind: fix intermittent build issues with high BR2_JLEVEL Jan Heylen
2015-11-05 21:42 ` Thomas Petazzoni [this message]
2015-11-06  7:04   ` Jan Heylen
2015-11-06  7:06     ` Jan Heylen
2015-11-06  9:19     ` Thomas Petazzoni
2016-01-06 21:10       ` Thomas De Schampheleire
2016-02-05 14:49         ` Thomas De Schampheleire
  -- strict thread matches above, loose matches on Subject: below --
2016-02-06  1:47 Ricardo Martincoski

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=20151105224203.77337e4b@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.