From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "Karicheri, Murali" <Murali.Karicheri@sandc.com>,
"Karicheri, Murali via buildroot" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Year 2038 time util issue - Build failure in 2024.02.x
Date: Wed, 17 Jul 2024 23:53:22 +0200 [thread overview]
Message-ID: <20240717235322.5f90b271@windsurf> (raw)
In-Reply-To: <b03840bf-6a53-4db7-ac58-ce1cc2587b8c@gmail.com>
Hello Florian,
On Wed, 17 Jul 2024 14:33:03 -0700
Florian Fainelli <f.fainelli@gmail.com> wrote:
> This looks similar to what I encountered a few days ago, the actual
> issue was that libsanitizer was referencing scsi/scsi.h (sorry about the
> message being in French, he he):
I think I should be able to read French :)
> ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:128:10:
> erreur fatale: scsi/scsi.h : No such file or directory
> 128 | #include <scsi/scsi.h>
> | ^~~~~~~~~~~~~
> compilation terminée.
I am not sure this is the same issue. Indeed, I don't see why this
missing <scsi/scsi.h> would be caused by BR2_TIME_BITS_64=y.
However, I see some host-gcc-final failures in our autobuilders that
seem related to BR2_TIME_BITS_64, such
as http://autobuild.buildroot.net/results/ff2/ff2dbfdabf0bb6a0d82ea8a80122ab97fd75bd3f/build-end.log:
/home/autobuild/autobuild/instance-0/output-1/host/i686-buildroot-linux-gnu/sysroot/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
I don't find your <scsi/scsi.h> issue in our autobuilders though. Do
you have a defconfig that reproduces the issue? <scsi/scsi.h> is
supposed to be installed by glibc.
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:[~2024-07-17 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 18:18 [Buildroot] Year 2038 time util issue - Build failure in 2024.02.x Karicheri, Murali via buildroot
2024-07-17 20:10 ` Thomas Petazzoni via buildroot
2024-07-17 21:33 ` Florian Fainelli
2024-07-17 21:53 ` Thomas Petazzoni via buildroot [this message]
2024-07-17 22:06 ` Florian Fainelli
2024-07-18 9:46 ` Thomas Petazzoni via buildroot
2024-07-18 20:05 ` Thomas Petazzoni via buildroot
2024-07-19 2:55 ` Florian Fainelli
2024-07-19 12:41 ` Thomas Petazzoni via buildroot
2024-07-18 14:57 ` [Buildroot] [External] " Karicheri, Murali via buildroot
2024-07-18 15:06 ` Karicheri, Murali via buildroot
2024-07-18 15:10 ` Karicheri, Murali via buildroot
2024-07-17 21:45 ` [Buildroot] " Karicheri, Murali via buildroot
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=20240717235322.5f90b271@windsurf \
--to=buildroot@buildroot.org \
--cc=Murali.Karicheri@sandc.com \
--cc=f.fainelli@gmail.com \
--cc=thomas.petazzoni@bootlin.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