All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Julien Olivain <ju.o@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: Sun, 14 Aug 2022 22:23:00 +0200	[thread overview]
Message-ID: <20220814202300.GM2854108@scaer> (raw)
In-Reply-To: <e0634cb156656205a84bc7ecce8a9412@free.fr>

Thomas, Julien, All,

On 2022-08-13 22:01 +0200, Julien Olivain spake thusly:
> On 13/08/2022 12:54, Thomas Petazzoni wrote:
> >On Sat, 13 Aug 2022 11:36:27 +0200
> >Julien Olivain <ju.o@free.fr> wrote:
> >>This commit also change the minimal supported kernel version from 3.10
> >>to 4.4. See [1].
> >Could this be problematic for some of our users? Do we want to keep
> >support for an older linux-backports release to still support 3.10
> >kernels?
> >
> >I can imagine that the people who end up using linux-backports are
> >probably stuck with an old kernel for some reason, so raising the
> >minimum kernel version required to use linux-backports is probably
> >something we should do with a bit of care?

But then, one could argue that this is the same with other packages that
get requirements on newer kernel headers (and thus probably about newer
running kernel). We can't hold back forever.

The alternate solution is not great: we could add a version choice:

    config BR2_PKG_LNX_BACKPORTS_5_15_X
        bool "5.15.x (for kernels back to 4.4)"

    config BR2_PKG_LNX_BACKPORTS_5_8_X
        bool "5.8.x (for kernels back to 3.10)"

But this is not ideal... :-/

> - 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?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-14 20:23 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 [this message]
2022-08-15  9:39       ` Thomas Petazzoni via buildroot
2022-08-15  9:52         ` Yann E. MORIN
2022-08-15 20:06       ` Julien Olivain
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=20220814202300.GM2854108@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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.