From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Maxim Kochetkov <fido_max@inbox.ru>,
Romain Naour <romain.naour@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC][PATCH 1/1] package/glibc: bump version to 2.34-5-g9995d0588f4f9adc68419224d2b3698e2ca4f77e
Date: Wed, 4 Aug 2021 21:30:19 +0200 [thread overview]
Message-ID: <20210804213019.6cf2a25d@windsurf> (raw)
In-Reply-To: <20210804172259.9143-1-petr.vorel@gmail.com>
Hello Petr,
On Wed, 4 Aug 2021 19:22:59 +0200
Petr Vorel <petr.vorel@gmail.com> wrote:
> Also upgrade to on RISC-V (that could have been done in d5ce3b5db5)
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> Hi,
>
> I tested it with building pc_x86_64_efi_defconfig, adding nfs-utils,
> ltp-testsuite and few other tools. Not sure if this is enough for
> testing.
I think that what Romain Naour typically does is run all qemu_*
defconfigs (of course tweaked to use glibc instead of uclibc), and push
them to Gitlab, so that they get build tested *and* boot tested under
Qemu.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-04 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 17:22 [Buildroot] [RFC][PATCH 1/1] package/glibc: bump version to 2.34-5-g9995d0588f4f9adc68419224d2b3698e2ca4f77e Petr Vorel
2021-08-04 19:30 ` Thomas Petazzoni [this message]
2021-08-18 19:46 ` Romain Naour
2021-08-18 21:53 ` Petr Vorel
2021-08-21 13:26 ` Romain Naour
2021-08-22 18:19 ` Petr Vorel
2021-08-04 21:35 ` Alistair Francis
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=20210804213019.6cf2a25d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fido_max@inbox.ru \
--cc=petr.vorel@gmail.com \
--cc=romain.naour@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox