All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Buildroot Notifications <buildroot.notifications@gmail.com>
Cc: buildroot@buildroot.org, Nadav Tasher <tashernadav@gmail.com>
Subject: Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2025-02-07
Date: Sat, 8 Feb 2025 05:46:34 +0100	[thread overview]
Message-ID: <20250208044634.GA1770044@pevik> (raw)
In-Reply-To: <67a6da1d.170a0220.15dee9.b177@mx.google.com>

Hi all,

> 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
> -------------------------------

> 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/

> Thanks for your contribution to Buildroot!
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2025-02-08  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <67a6da1d.170a0220.15dee9.b177@mx.google.com>
2025-02-08  4:46 ` Petr Vorel [this message]
2025-02-08 15:39   ` [Buildroot] [autobuild.buildroot.org] Your daily results for 2025-02-07 Nadav Tasher

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=20250208044634.GA1770044@pevik \
    --to=petr.vorel@gmail.com \
    --cc=buildroot.notifications@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=tashernadav@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.