Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] bind: fix intermittent build issues with high BR2_JLEVEL
Date: Sat, 6 Feb 2016 10:52:40 +0100	[thread overview]
Message-ID: <20160206105240.7a7694a8@free-electrons.com> (raw)
In-Reply-To: <1454749207-23363-1-git-send-email-heyleke@gmail.com>

Dear Jan Heylen,

On Sat,  6 Feb 2016 10:00:07 +0100, Jan Heylen wrote:
> 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.
> 
> [Jan Heylen: This patch was removed with commit c36b5d89c5616f7ca0a7295cbb5c231606beb71e
> by Gustavo Zacarias <gustavo@zacarias.com.ar> but the problem still occurs,
> so disabling parallel builds again]

When a patch is your own patch, there is no need to put such comments
between [<your name>: ...]. It's only when you take over the patch of
someone else. So I've kept this comment in the commit log, without the
[<your name>: ...] around it.

Applied, thanks!

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

      reply	other threads:[~2016-02-06  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06  9:00 [Buildroot] [PATCH v3] bind: fix intermittent build issues with high BR2_JLEVEL Jan Heylen
2016-02-06  9:52 ` Thomas Petazzoni [this message]

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=20160206105240.7a7694a8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox