From: Peter Korsgaard <peter@korsgaard.com>
To: Niklas Cassel via buildroot <buildroot@buildroot.org>
Cc: Niklas Cassel <niklas.cassel@wdc.com>,
damien.lemoal@opensource.wdc.com, alistair@alistair23.me,
geert@linux-m68k.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
romain.naour@smile.fr, yann.morin.1998@free.fr
Subject: Re: [Buildroot] [PATCH v2 2/2] package/elf2flt: fix fatal error regression on m68k, xtensa, riscv64
Date: Thu, 15 Sep 2022 09:21:52 +0200 [thread overview]
Message-ID: <87leqlm7an.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220811094049.798010-3-niklas.cassel@wdc.com> (Niklas Cassel via buildroot's message of "Thu, 11 Aug 2022 11:40:49 +0200")
>>>>> "Niklas" == Niklas Cassel via buildroot <buildroot@buildroot.org> writes:
> This series fixes a fatal error at link time on m68k, xtensa,
> and riscv64, caused by a bad upstream elf2flt commit.
> Without this patch, m68k, xtensa, and riscv64 would result in
> a fatal error:
> ERROR: text=0x3bab8 overlaps data=0x33f60 ?
> With this patch, qemu_m68k_mcf5208_defconfig,
> qemu_riscv64_nommu_virt_defconfig, and
> qemu_xtensa_lx60_nommu_defconfig builds properly.
> riscv64 and m68k boots to login prompt.
> xtensa crashes when loading init, the same behavior as when
> reverting the bad upstream elf2flt commit completely.
> Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
When was this regression introduced? With the update to elf2flt 2021.08?
Are 2022.02.x and 2022.05.x also affected?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-15 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 9:40 [Buildroot] [PATCH v2 0/2] fix elf2flt on m68k, xtensa, riscv Niklas Cassel via buildroot
2022-08-11 9:40 ` [Buildroot] [PATCH v2 1/2] package/elf2flt: remove broken patch Niklas Cassel via buildroot
2022-08-11 9:40 ` [Buildroot] [PATCH v2 2/2] package/elf2flt: fix fatal error regression on m68k, xtensa, riscv64 Niklas Cassel via buildroot
2022-08-11 20:30 ` Thomas Petazzoni via buildroot
2022-08-12 0:02 ` Max Filippov
2022-09-15 7:21 ` Peter Korsgaard [this message]
2022-09-15 11:18 ` Niklas Cassel via buildroot
2022-09-15 14:01 ` Peter Korsgaard
2022-08-11 20:28 ` [Buildroot] [PATCH v2 0/2] fix elf2flt on m68k, xtensa, riscv Thomas Petazzoni via buildroot
2022-09-23 20:40 ` Thomas Petazzoni via buildroot
2023-01-17 15:45 ` Niklas Cassel 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=87leqlm7an.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=alistair@alistair23.me \
--cc=buildroot@buildroot.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=geert@linux-m68k.org \
--cc=niklas.cassel@wdc.com \
--cc=romain.naour@smile.fr \
--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.