Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-14
Date: Sun, 16 Dec 2018 09:17:54 +0100	[thread overview]
Message-ID: <20181216091754.66bb0ec6@windsurf.home> (raw)
In-Reply-To: <87zht69k2o.fsf@tkos.co.il>

Hello,

On Sun, 16 Dec 2018 06:22:55 +0200, Baruch Siach wrote:

> > Makefile.legacy:9: *** "You have legacy configuration in your .config!
> > Please check your configuration.".  Stop.
> > Makefile:84: recipe for target '_all' failed
> > make: *** [_all] Error 2  
> 
> This is most likely because of the BR2_TARGET_GENERIC_PASSWD_MD5 symbol
> that has recently been added to Config.in.legacy. You can use the
> defconfig instead. Here is what I usually do:
> 
>   wget -O .config http://autobuild.buildroot.net/results/71c46fac3bd30c7d30ac89ce43e411a9772665bb/defconfig
>   make olddefconfig

Also, to reproduce a build failure, one can use the following script:

  http://git.buildroot.net/buildroot-test/plain/utils/br-reproduce-build

Like this:

  ./br-reproduce-build 71c46fac3bd30c7d30ac89ce43e411a9772665bb

It makes sure to checkout the right Buildroot commit, on which the
build failure occurred.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-12-16  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181215070019.5B30D20CE3@mail.bootlin.com>
2018-12-15 21:29 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-12-14 Bartosz Golaszewski
2018-12-16  4:22   ` Baruch Siach
2018-12-16  8:17     ` 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=20181216091754.66bb0ec6@windsurf.home \
    --to=thomas.petazzoni@bootlin.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