From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: buildroot@buildroot.org
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 0/2 v2] linux|uboot: fix build with host-gcc 10+ for older versions (branch yem/yylloc)
Date: Mon, 31 Jan 2022 22:38:06 +0100 [thread overview]
Message-ID: <cover.1643665029.git.yann.morin.1998@free.fr> (raw)
Hello All!
This two-patch series aims at side-stepping the multiple symbol
declaration in older Linux and U-Boot, where the infamous yylloc is
defined more than once.
Like we have a fix for the perl timeconst issue in linux, do s similar
tweak for yylloc in the two packages known to be affected, Linux and
U-Boot.
Here is a pipeline with all the defconfig builds:
https://gitlab.com/ymorin/buildroot/-/pipelines/460207930
There are still some failures, but none relate to the yylloc issue:
- too long build time or not space left on device (I am only using
elastic runners)
- defconfig not up-to-date (e.g. using kernel headers version since
removed)
- missing host dependencies for kernel (openssl, libelf) or uboot
(python)
- another host-gcc 10+ symbol redefinition issue (galileo [0])
- make 4.3 issues. For example: amarula_a64_relic_defconfig
https://gitlab.com/ymorin/buildroot/-/jobs/2035820886
DTC arch/arm/dts/sun50i-a64-amarula-relic.dtb
Error: arch/arm/dts/.sun50i-a64-amarula-relic.dtb.pre.tmp:66.1-10 syntax error
FATAL ERROR: Unable to parse input tree
This is caused by make 4.3 that no longer treats '#' as special in
macros, and shall no longer be escaped:
https://lwn.net/Articles/810071/
This causes '\#include "something"' to be injected as-is at the end
of the temporary DTS, and of course, dtc does not cope nicely with
that... [1]
Unfortuantely, I don't think we can do a generic fixup for that
one...
- some other issues (e.g. deprecated 'partition-type' for geniamge..)
[0] this was fixed in 2014 in the kernel:
- eeeda4cd06e828b331b15741a204ff9f5874d28d
[1] this was fixed in 2018 in uboot:
- e5e701c2b8470de044c5c71d2a54ecfc72680d59
- 0c544115379ed77c1843a194e26960e5b8f3d369
Changes v1 -> v2:
- don't fail if no file to fix: use 'grep -Z |xargs -0 -r' (Arnout)
- extend cover-ltter with a pipeline reference and analysese of
remaining build failures
Regards,
Yann E. MORIN.
----------------------------------------------------------------
Yann E. MORIN (2):
boot/uboot: fix build with host-gcc 10+
linux: fix build with host-gcc 10+
boot/uboot/uboot.mk | 7 +++++++
linux/linux.mk | 7 +++++++
2 files changed, 14 insertions(+)
--
.-----------------.--------------------.------------------.--------------------.
| 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
next reply other threads:[~2022-01-31 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 21:38 Yann E. MORIN [this message]
2022-01-31 21:38 ` [Buildroot] [PATCH 1/2 v2] boot/uboot: fix build with host-gcc 10+ Yann E. MORIN
2022-02-04 10:40 ` Giulio Benetti
2022-02-27 19:24 ` Peter Korsgaard
2022-01-31 21:38 ` [Buildroot] [PATCH 2/2 v2] linux: " Yann E. MORIN
2022-01-31 22:10 ` Peter Seiderer
2022-02-04 10:41 ` Giulio Benetti
2022-02-27 19:24 ` Peter Korsgaard
2022-02-12 20:38 ` [Buildroot] [PATCH 0/2 v2] linux|uboot: fix build with host-gcc 10+ for older versions (branch yem/yylloc) Arnout Vandecappelle
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=cover.1643665029.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox