From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Huth <huth@tuxfamily.org>
Cc: Louis Aussedat <aussedat.louis@gmail.com>,
Filip Skoneczny <fskoneczny@gmail.com>,
Marek Belisko <marek.belisko@open-nandra.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Davide Viti <zinosat@gmail.com>,
Mike Harmony <mike.harmony@snapav.com>,
Peter Seiderer <ps.report@gmx.net>,
Jagan Teki <jagan@amarulasolutions.com>,
Suniel Mahesh <sunil@amarulasolutions.com>,
Heiko Thiery <heiko.thiery@gmail.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] Buildroot defconfigs about to be removed
Date: Mon, 8 Aug 2022 10:26:53 +0200 [thread overview]
Message-ID: <20220808102653.5a7a0584@windsurf> (raw)
In-Reply-To: <20220808101452.566fd732@tuxfamily.org>
Hello Thomas,
On Mon, 8 Aug 2022 10:14:52 +0200
Thomas Huth <huth@tuxfamily.org> wrote:
> > qemu_xtensa_lx60_nommu_defconfig -> elf2flt segfaults
> > https://gitlab.com/buildroot.org/buildroot/-/jobs/2812053940
> >
> > qemu_m68k_mcf5208_defconfig -> elf2flt segfaults
> > https://gitlab.com/buildroot.org/buildroot/-/jobs/2812053827
>
> I'm interested in keeping the qemu defconfigs alive, please don't remove
> them yet. I'll try to figure out what's going wrong here.
So these are "special" issues. The elf2flt segfault is caused by the
changes in elf2flt to support RISC-V 64-bit noMMU, in commit
32f93b0ef2c602dfa1f5b243ba865d5b16e2fa33.
However, even with this removed, we have issues with elf2flt. See
https://lore.kernel.org/buildroot/20220725164425.7316b2e3@windsurf/ for
more details, and also
https://lore.kernel.org/buildroot/ce677d88-8f8e-2d81-4e7b-69a35a99c6b9@smile.fr/.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-08 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 20:43 [Buildroot] Buildroot defconfigs about to be removed Thomas Petazzoni via buildroot
2022-08-06 22:28 ` Heiko Thiery
2022-08-08 8:28 ` Thomas Petazzoni via buildroot
2022-08-12 6:32 ` Suniel Mahesh
2022-08-08 8:14 ` Thomas Huth
2022-08-08 8:26 ` Thomas Petazzoni via buildroot [this message]
2022-08-08 19:59 ` Thomas Huth
2022-08-12 13:52 ` Thomas Petazzoni via buildroot
2022-08-15 9:50 ` Thomas Huth
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=20220808102653.5a7a0584@windsurf \
--to=buildroot@buildroot.org \
--cc=aussedat.louis@gmail.com \
--cc=fskoneczny@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=heiko.thiery@gmail.com \
--cc=huth@tuxfamily.org \
--cc=jagan@amarulasolutions.com \
--cc=marek.belisko@open-nandra.com \
--cc=mike.harmony@snapav.com \
--cc=ps.report@gmx.net \
--cc=romain.naour@gmail.com \
--cc=sunil@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
--cc=zinosat@gmail.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.