All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain <ju.o@free.fr>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 1/1] package/linux-backports: bump version to 5.15.58
Date: Mon, 15 Aug 2022 22:06:55 +0200	[thread overview]
Message-ID: <4030b275fb04cbdc96c325c62d49a11e@free.fr> (raw)
In-Reply-To: <20220814202300.GM2854108@scaer>

Hi Yann, Thomas, All,

On 14/08/2022 22:23, Yann E. MORIN wrote:
> Thomas, Julien, All,
> 
> On 2022-08-13 22:01 +0200, Julien Olivain spake thusly:
[...]
>> - Trying to compile kernel v3.10.108 in qemu_aarch64_virt_defconfig
>>   did not worked out-of-the-box for me (on Buildroot tag
>>   2022.08-rc1, in utils/docker-run). Build fails with:
>> 
>>     dtc-lexer.lex.c: In function 'yylex':
>>     dtc-lexer.l:46:18: error: 'yylloc' undeclared (first use in this
>> function); did you mean 'yyalloc'?
> 
> Gah. This is 9b41b54be077 (linux: fix build with host-gcc 10+)...
> 
> That's because in 3.10, the dtc sub-dir still had the pre-generated
> lexer and parser. And with 9b41b54be077, we remove all lines that
> instanciate yylloc as a YYLTYPE:
> 
>     grep -Z -l -r -E '^YYLTYPE yylloc;$$' $(@D) \
>     |xargs -0 -r $(SED) '/^YYLTYPE yylloc;$$/d'
> 
> So, this will remove it in bot the actual source and the pre-generated 
> C
> files.
> 
> So, yeah, we might even be able to build a 3.10 kernel with 
> contemporary
> Buildroot versions anyway...
> 
> We could fix that by passing REGENERATE_PARSERS=1 in 
> LINUX_MAKE_FLAGS...
> Julien, could you test that, please?

I quickly tried adding REGENERATE_PARSERS=1 in LINUX_MAKE_FLAGS.
It's still failing with:

     dtc-lexer.lex.c: In function 'yylex':
     dtc-lexer.l:46:18: error: 'yylloc' undeclared (first use in this 
function); did you mean 'yyalloc'?
     [...]
     dtc-parser.y: In function 'print_error':
     dtc-parser.y:478:17: error: 'yylloc' undeclared (first use in this 
function); did you mean 'yyalloc'?
     dtc-parser.y:478:17: note: each undeclared identifier is reported 
only once for each function it appears in

I'll investigate later.

In order to test that thoroughly, what is the oldest kernel we would 
like to compile
out-of-the-box in Buildroot?  v3.0?

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-08-15 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13  9:36 [Buildroot] [PATCH next 1/1] package/linux-backports: bump version to 5.15.58 Julien Olivain
2022-08-13 10:54 ` Thomas Petazzoni via buildroot
2022-08-13 20:01   ` Julien Olivain
2022-08-14 20:23     ` Yann E. MORIN
2022-08-15  9:39       ` Thomas Petazzoni via buildroot
2022-08-15  9:52         ` Yann E. MORIN
2022-08-15 20:06       ` Julien Olivain [this message]
2022-08-15  9:51 ` Thomas Petazzoni via buildroot

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=4030b275fb04cbdc96c325c62d49a11e@free.fr \
    --to=ju.o@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.