From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading my defconfig
Date: Tue, 10 Jun 2014 21:47:57 +0200 [thread overview]
Message-ID: <20140610214757.75cd4ec7@free-electrons.com> (raw)
In-Reply-To: <CAE9DZUS6HUUFpt-Rm-WONCcx5_4y+F+8TtcPFYzuNCfiraq83Q@mail.gmail.com>
Dear Dallas Clement,
On Tue, 10 Jun 2014 11:11:24 -0500, Dallas Clement wrote:
> Hi All, Would someone kindly guide me through the steps of upgrading my
> defconfig? It's a few years out of date. I've upgraded the rest of
> buildroot itself, and when I try to save my defconfig the makefile
> complains bitterly:
>
> $ make savedefconfig
> Makefile.legacy:12: *** "You have legacy configuration in your .config!
> Please check your configuration.". Stop.
I know you replied to your own e-mail, but for the record: this means
your configuration has old Buildroot options that have been removed
since then. You should therefore run "make menuconfig", and look into
the "Legacy options" submenu to see which old options you're using.
Buildroot wants you to disable them manually so that you're aware of
their disappearance, and you have some help on how to migrate to the
new name of the option if applicable.
We should probably change the error message here to something more
explanatory.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-10 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 16:11 [Buildroot] Upgrading my defconfig Dallas Clement
2014-06-10 17:30 ` Dallas Clement
2014-06-10 19:47 ` Thomas Petazzoni [this message]
2014-06-10 20:21 ` Dallas Clement
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=20140610214757.75cd4ec7@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