[Buildroot] [RFC][PATCH 1/1] package/glibc: bump version to 2.34-5-g9995d0588f4f9adc68419224d2b3698e2ca4f77e

Romain Naour romain.naour at gmail.com
Wed Aug 18 19:46:29 UTC 2021


Hello,

Le 04/08/2021 à 21:30, Thomas Petazzoni a écrit :
> Hello Petr,
> 
> On Wed,  4 Aug 2021 19:22:59 +0200
> Petr Vorel <petr.vorel at gmail.com> wrote:
> 
>> Also upgrade to on RISC-V (that could have been done in d5ce3b5db5)
>>
>> Signed-off-by: Petr Vorel <petr.vorel at 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.

Indeed, the runtime test is only a boot test. I've looked at the glibc testsuite
but it's difficult to setup with a cross-compiled system running under Qemu in a
CI (glitlab).

For testing, upstream suggest to use a NFS to share the glibc sources between
the host and the target (not very handy):
https://sourceware.org/glibc/wiki/Testing/Testsuite

Some tests requires a minimal amount of RAM that is not always provided by Qemu
target.

There is also libc-test project from musl project:
https://wiki.musl-libc.org/libc-test.html

Indeed running some tests from ltp-testsuite would be better than nothing.
On the other hand we can detect enough boot issue related to toolchain upgrade
to keep us busy.

Best regards,
Romain

> 
> Thomas
> 



More information about the buildroot mailing list