From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@uclibc.org
Subject: [Buildroot] Upgrading buildroot and rootfs/kernel compatibility
Date: Fri, 13 Sep 2024 19:29:52 -0000 (UTC) [thread overview]
Message-ID: <vc23rg$llm$1@ciao.gmane.io> (raw)
I started with a buildroot 2020.02.7 configuration provided by a
silicon vendor that used a linaro-6.3.1-2017.02 toolchain. That
worked OK after I manually upgraded a couple packages that were too
old to build using my host system's gcc 13.3.
Now I'm trying to upgrade buildroot to 2024.02.6. First I tried using
the same toolchain as above. That failed. AFAICT, it was because
Fortran support was enabled in the toolchain, and BF 2024 can't
tolerate that unless Fortran support is also enabled somewhere else
(it wasn't clear where).
Then I tried the "standard" external toolchains listed in the
2024.02.6 menuconfig.
ARM
With arm-gnu-toolchain-13.2.rel1 the rootfs built cleanly, but the
target panicked as soon as the init process was started. I assume
that's some sort of Linux system-call incompatibility between the
glibc included in the ARM toolchain and my 4.19.142 kernel (which I
think was built using buildroot 2020 -- probably using the Linaro
6.3.1-2017.02 toolchain).
Linaro
With the linaro-7.3.1-2018.05 toolchain, the rootfs builds cleanly
and the resulting image appears to work, though it's about 20%
larger than before with the same set of packages selected. Is that
sort of size increase typical? (I know, it depends on the
packages.)
What I'm trying to understand is where rootfs/kernel incompatibilities
come from.
* Did the rootfs built with the ARM compiler crash because the kernel
headers used by ARM to build glibc were incompatible with my
kernel?
* Is the gcc 13.2 compiler version itself incompatible with my kernel
version? (Would it fail even if glibc could be built using gcc
13.2 and my kernel headers).
* Are some versions of glibc simply not compatible with some kernel
versions regardless of the toolchain and kernel headers used to
build glibc?
--
Grant
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-09-13 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 19:29 Grant Edwards [this message]
2024-09-14 7:43 ` [Buildroot] Upgrading buildroot and rootfs/kernel compatibility Thomas Petazzoni via buildroot
2024-09-14 22:02 ` Grant Edwards
2024-09-15 9:55 ` Edgar Bonet
2024-09-15 1:24 ` Grant Edwards
2024-09-18 16:46 ` Grant Edwards
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='vc23rg$llm$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@uclibc.org \
/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