From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] kconfig: update to Linux 5.2-rc4
Date: Tue, 11 Jun 2019 19:20:32 +0900 [thread overview]
Message-ID: <CAK7LNASykybkHnXa_CO6X=rpVwhtBmzjg2+kL=J48jC7hoJt3w@mail.gmail.com> (raw)
In-Reply-To: <20190611090758.j5sr7zzgkdibxhbm@pengutronix.de>
Hi Sascha,
On Tue, Jun 11, 2019 at 6:08 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> Hi,
> On Mon, Jun 10, 2019 at 05:47:04PM +0900, Masahiro Yamada wrote:
> > The previous sync was Linux 4.20. This updates Kconfig to Linux 5.2-rc4.
> >
> > I adjusted the top Makefile as well because Linux commit 058507195b53
> > ("kbuild: move ".config not found!" message from Kconfig to Makefile")
> > moved the .config check from Kconfig to Makefile.
> >
> > I also made auto.conf a mandatory include file, and remove it from the
> > prerequisites of other targets. We are safe because Make is immediately
> > terminated when syncconfig fails to generate auto.conf.
>
> This doesn't work with out of tree builds, but it looks like it's not the
> fault of this series make menuconfig fails with:
>
> gcc -Wp,-MD,scripts/kconfig/.parser.tab.o.d -Iscripts/kconfig -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer /full/path/omitted/barebox/scripts/kconfig -c -o
> scripts/kconfig/parser.tab.o scripts/kconfig/parser.tab.c
> scripts/kconfig/parser.tab.c:79:10: fatal error: lkc.h: No such file or directory
>
> As you can see the -I is missing before the "/full/path/..." string.
>
> With this change:
>
> -HOSTCFLAGS_lexer.lex.o := -I $(srctree)/$(src)
> -HOSTCFLAGS_parser.tab.o := -I $(srctree)/$(src)
> +HOSTCFLAGS_lexer.lex.o := -I$(srctree)/$(src)
> +HOSTCFLAGS_parser.tab.o := -I$(srctree)/$(src)
>
> it works as expected. I have no idea why this is happening. Could you
> have a look?
My bad - I forgot that the nasty 'addtree' is still remaining in barebox.
It is gone from the latest Linux, but we need treewide Makefile cleanups
to kill it.
I just cherry-picked 48f6e3cf5bc6dd0ee00405342ff310c3b1fedb35
to move forward with a minimal change.
--
Best Regards
Masahiro Yamada
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-06-11 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:47 Masahiro Yamada
2019-06-11 9:07 ` Sascha Hauer
2019-06-11 10:20 ` Masahiro Yamada [this message]
2019-06-17 7:05 ` Sascha Hauer
2019-06-17 8:02 ` Masahiro Yamada
2019-06-18 7:11 ` Sascha Hauer
2019-06-18 7:24 ` Masahiro Yamada
2019-06-19 8:11 ` Sascha Hauer
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='CAK7LNASykybkHnXa_CO6X=rpVwhtBmzjg2+kL=J48jC7hoJt3w@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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