Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: 2015.07 - fix creation of .config
Date: Mon, 17 Aug 2015 09:58:34 +0000	[thread overview]
Message-ID: <1439805514.3667.31.camel@synopsys.com> (raw)
In-Reply-To: <20150817093130.GA3988@free.fr>

Hi Yann,

On Mon, 2015-08-17 at 11:31 +0200, Yann E. MORIN wrote:
> Alexey, All,
> 
> On 2015-08-17 06:37 +0000, Alexey Brodkin spake thusly:
> > On Sun, 2015-08-16 at 23:43 +0200, J?rg Krause wrote:
> > > Hi Thomas, Alexey,
> > > 
> > > On Mi, 2015-08-12 at 10:23 +0200, Thomas Petazzoni wrote:
> > > > Dear Alexey Brodkin,
> > > > 
> > > > On Tue, 11 Aug 2015 12:20:01 +0000, Alexey Brodkin wrote:
> > > > 
> > > > > Any chance for this one to be applied?
> > > > > Note without this change or anything similar U-Boot from
> > > > > snsp_axs10x_defconfig fails to config.
> > > > 
> > > > I haven't had the time to look into this in detail. It would be great
> > > > if Yann, or J?rg could have a look. I remain unhappy with solving
> > > > such
> > > > a problem by using a patch against U-Boot 2015.07, because it means
> > > > anyone specifying a slightly different U-Boot version (but based on
> > > > 2015.07) will still have the problem.
> > > 
> > > It looks like upstream [1] does not revert this patch but fixes the
> > > problem with this patch [2]. Alexey, does this patch solves your
> > > problem?
> > > 
> > > Best regards
> > > J?rg Krause
> > > 
> > > 
> > > [1]
> > > https://www.mail-archive.com/u-boot at lists.denx.de/msg179681.html 
> > > 
> > > [2]
> > > http://patchwork.ozlabs.org/patch/502793/
> > 
> > The thing is [2] solves problem only for ARM, while other arches are still
> > affected. And that means ARC is not cured by that patch.
> > 
> > Indeed proper fix is to patch all arches in the same way,
> > i.e. select default option for each and every architecture in U-Boot.
> > 
> > But speaking about Buildroot that approach has at least 2 downsides:
> >  1) Not all arches are fixed upstream so in Buildroot we'll have patches
> >     that are not there in upstream yet.
> > 
> >  2) We'll have quite a few patches in Buildroot for U-boot each fixing
> >     a separate arch.
> > 
> > If (1) and (2) are OK for Buildroot I'll try to come up with those patches ASAP.
> > 
> > My initial approach was IMHO the cleanest and simplest. But if it doesn't work
> > we'll do another fix :)
> 
> OK, chiming in...
> 
> I guess removing the "optional" keywork would be the simplest solution,
> indeed.
> 
> But then I'm afraid that defconfig files bundled with U-Boot will no
> longer work. If they still work, then I'm OK for having a local patch
> that reverts upstream's (until upstream fixes all of their archs).

Ok that's probably another mystery of Kconfig but defconfigs bundled with
U-Boot do work. They worked both before reverted patch and after.

What doesn't work is "make oldconfig".
See in U-Boot (let's forget about Buildroot for a minute) we usually build stuff
with defconfigs this way "make xxx_defconfig". And it worked and it works still.

But in Buildroot what we do we take "xxx_deconfig", copy it from "configs" folder
to the root of U-Boot build folder as .config, do changes we need and then to get
correctly expanded .config for building we finally do "make oldconfig".

And that's where the problem happens. Kconfig just skips items marked as optional
and so platforms are not set properly and build fails.

In other words I would blame Kconfig and I even spent some time trying to
figure out if there's a way to fix Kconfig simply. But to no avail. And so
I decided to work-around Kconfig issue.

Hope that comment makes sense.

-Alexey

  reply	other threads:[~2015-08-17  9:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 14:04 [Buildroot] [PATCH] u-boot: 2015.07 - fix creation of .config Alexey Brodkin
2015-07-31 14:18 ` Thomas Petazzoni
2015-07-31 15:14   ` Alexey Brodkin
2015-08-03 11:16     ` Alexey Brodkin
2015-08-11 12:20       ` Alexey Brodkin
2015-08-12  8:23         ` Thomas Petazzoni
2015-08-16 21:43           ` Jörg Krause
2015-08-17  6:37             ` Alexey Brodkin
2015-08-17  9:31               ` Yann E. MORIN
2015-08-17  9:58                 ` Alexey Brodkin [this message]
2015-08-22 22:57           ` Arnout Vandecappelle
2015-08-28  9:36             ` Alexey Brodkin
2015-08-30 20:41             ` Peter Korsgaard
2015-08-30 20:51 ` Peter Korsgaard
2015-08-31 16:43   ` Alexey Brodkin

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=1439805514.3667.31.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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