Skip to contentSkip to conversation

Your daily results for 2025-02-07

Buildroot Petr Vorel 2 participants 2 messages Feb 8, 2025 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Petr Vorel

author
#1 lore raw

Hi all,

Quoted 13 lines

Hello,

Autobuilder failures
====================

Below is a list of build failures reported by the Buildroot autobuilders in relation to packages or CPU architectures you are in charge of. Please help us improving the quality of Buildroot by investigating those build failures and sending patches to fix them.

Results for the 'master' branch
-------------------------------

Quoted 7 lines

Build failures related to your packages:

arch | reason | url
-------------+--------------------------------+---------------------------------------------------------------------------------

    arc      |     ltp-testsuite-20250130     | https://autobuild.buildroot.org/results/609697d89e0c5948842c7c0e5dcec4d93be3258e
   arceb     |     ltp-testsuite-20250130     | https://autobuild.buildroot.org/results/8814f6f166ad6ddd58e8627964d147ecfff4d76f
   xtensa    |     ltp-testsuite-20250130     | https://autobuild.buildroot.org/results/05728d3609553a0b78875d62adb88cccb43e00ed

All are uclibc-ng, problem. Nadav suggests [1] it's caused by the fact that time64 on 32-bit targets is not supported on Linux < 5.1.0. I'm not sure why this is just on uclibc-ng. Should I bump min kernel headers for uclibc-ng >= 5.1.0?

Kind regards,
Petr

[1] https://lore.kernel.org/ltp/Z5q7NwweeZ0iNlzc@nadav-dell/

Quoted 1 line

Thanks for your contribution to Buildroot!

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

#2 lore raw
Quoted 23 lines · Petr Vorel

Hi all,

Quoted 13 lines

Hello,

Autobuilder failures
====================

Below is a list of build failures reported by the Buildroot autobuilders in relation to packages or CPU architectures you are in charge of. Please help us improving the quality of Buildroot by investigating those build failures and sending patches to fix them.

Results for the 'master' branch
-------------------------------

Quoted 7 lines

Build failures related to your packages:

arch | reason | url
-------------+--------------------------------+---------------------------------------------------------------------------------

    arc      |     ltp-testsuite-20250130     | https://autobuild.buildroot.org/results/609697d89e0c5948842c7c0e5dcec4d93be3258e
   arceb     |     ltp-testsuite-20250130     | https://autobuild.buildroot.org/results/8814f6f166ad6ddd58e8627964d147ecfff4d76f
   xtensa    |     ltp-testsuite-20250130     | https://autobuild.buildroot.org/results/05728d3609553a0b78875d62adb88cccb43e00ed
Quoted 10 lines

All are uclibc-ng, problem. Nadav suggests [1] it's caused by the fact that time64 on 32-bit targets is not supported on Linux < 5.1.0. I'm not sure why this is just on uclibc-ng. Should I bump min kernel headers for uclibc-ng >= 5.1.0?

Kind regards,
Petr

[1] https://lore.kernel.org/ltp/Z5q7NwweeZ0iNlzc@nadav-dell/

Quoted 1 line

Thanks for your contribution to Buildroot!

Hi Petr,
Linux 5.1.0 is only the minimal headers version when TIME64 is enabled for uclibc-ng.
Is there a way to make it so that it is only affected when TIME64 is enabled? I think this would be a little complicated since TIME64 is enabled by default.

I guess making 5.1.0 the minimal for uclibc-ng would solve the issue, but it might impose some limitations for people trying to compile newer versions of Buildroot with older versions of Linux.

Nadav
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot