From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Karicheri, Murali via buildroot" <buildroot@buildroot.org>
Cc: "Karicheri, Murali" <Murali.Karicheri@sandc.com>
Subject: Re: [Buildroot] Year 2038 time util issue - Build failure in 2024.02.x
Date: Wed, 17 Jul 2024 22:10:00 +0200 [thread overview]
Message-ID: <20240717221000.5ced2d0d@windsurf> (raw)
In-Reply-To: <DM4PR02MB9216BC15AD2F3FEE125A71118AA32@DM4PR02MB9216.namprd02.prod.outlook.com>
Hello Murali,
On Wed, 17 Jul 2024 18:18:35 +0000
"Karicheri, Murali via buildroot" <buildroot@buildroot.org> wrote:
> We were using buildroot version 2023.08 version and encountered a
> year 2038 crash when using time/date utilities. So, my research found
> some work done in the recent version of buildroot. Where
> BR2_TIME_BITS_64=y was added to build with 64bit time field. My board
> is based on a STM32MP133c SoC and using an external project to build
> buildroot. So, I have migrated our project to using 2024.02.x version
> of buildroot and enabled BR2_TIME_BITS_64=y to get the fix for the
> 2038 issue. But my build fails with the logs below.
Sorry to hear that your build fails with Buildroot 2024.02.x. See below
some details.
>
> Could you help me answer the following questions?
> 1. Is the Y2038 time issue resolved in buildroot? If not, is there
> some work, though officially not supported, I can investigate for a
> potential solution
Things are not as black and white as "Is the Y2038 time issue
resolved". How 64-bit time_t is handled depends on the C library, and
also different packages might exhibit different problems. So it's not
like we can absolutely guarantee that everything is fixed.
> 2. If it is in fact resolved and expected to work in 2024.02.x, what
> I might be missing? Is there specific version of the toolchain
> packages I need to select in the Toolchain configuration and other
> packages?
We expect things to work, but we have lots of packages.
> libtool: compile: /src/linux-bsp-stm32mp133c/output/development/build/host-gcc-final-12.3.0/build/./gcc/xgcc -shared-libgcc -B/src/linux-bsp-stm32mp133c/output/development/build/host-gcc-final-12.3.0/build/./gcc -nostdinc++ -L/src/linux-bsp-stm32mp133c/output/development/build/host-gcc-final-12.3.0/build/arm-buildroot-linux-gnueabihf/libstdc++-v3/src -L/src/linux-bsp-stm32mp133c/output/development/build/host-gcc-final-12.3.0/build/arm-buildroot-linux-gnueabihf/libstdc++-v3/src/.libs -L/src/linux-bsp-stm32mp133c/output/development/build/host-gcc-final-12.3.0/build/arm-buildroot-linux-gnueabihf/libstdc++-v3/libsupc++/.libs -B/src/linux-bsp-stm32mp133c/output/development/host/arm-buildroot-linux-gnueabihf/bin/ -B/src/linux-bsp-stm32mp133c/output/development/host/arm-buildroot-linux-gnueabihf/lib/ -isystem /src/linux-bsp-stm32mp133c/output/development/host/arm-buildroot-linux-gnueabihf/include -isystem /src/linux-bsp-stm32mp133c/output/development/host/arm-buildroot-linux-gnueabihf/sy
s-
> include -D_GNU_SOURCE -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -DHAVE_RPC_XDR_H=0 -DHAVE_TIRPC_RPC_XDR_H=0 -I. -I../../../../libsanitizer/sanitizer_common -I.. -I ../../../../libsanitizer/include -I ../../../../libsanitizer -isystem ../../../../libsanitizer/include/system -Wall -W -Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long -fPIC -fno-builtin -fno-exceptions -fno-rtti -fomit-frame-pointer -funwind-tables -fvisibility=hidden -Wno-variadic-macros -I../../libstdc++-v3/include -I../../libstdc++-v3/include/arm-buildroot-linux-gnueabihf -I../../../../libsanitizer/../libstdc++-v3/libsupc++ -std=gnu++14 -DSANITIZER_LIBBACKTRACE -DSANITIZER_CP_DEMANGLE -I ../../../../libsanitizer/../libbacktrace -I ../libbacktrace -I ../../../../libsanitizer/../include -include ../../../../libsanitizer/libbacktrace/backtrace-rename.h -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Og -g2 -D_GNU_SOURCE -MT sanitizer_p
ro
> cmaps_common.lo -MD -MP -MF .deps/sanitizer_procmaps_common.Tpo -c ../../../../libsanitizer/sanitizer_common/sanitizer_procmaps_common.cpp -o sanitizer_procmaps_common.o >/dev/null 2>&1
> mv -f .deps/sanitizer_linux_libcdep.Tpo .deps/sanitizer_linux_libcdep.Plo
> mv -f .deps/sanitizer_procmaps_linux.Tpo .deps/sanitizer_procmaps_linux.Plo
> mv -f .deps/sanitizer_linux.Tpo .deps/sanitizer_linux.Plo
> mv -f .deps/sanitizer_printf.Tpo .deps/sanitizer_printf.Plo
> mv -f .deps/sanitizer_posix.Tpo .deps/sanitizer_posix.Plo
> mv -f .deps/sanitizer_procmaps_common.Tpo .deps/sanitizer_procmaps_common.Plo
> mv -f .deps/sanitizer_posix_libcdep.Tpo .deps/sanitizer_posix_libcdep.Plo
> make[6]: *** [Makefile:533: all-recursive] Error 1
> make[5]: *** [Makefile:420: all] Error 2
> make[4]: *** [Makefile:13138: all-target-libsanitizer] Error 2
> make[3]: *** [Makefile:1033: all] Error 2
> make[2]: *** [package/pkg-generic.mk:283: /src/linux-bsp-stm32mp133c/output/development/build/host-gcc-final-12.3.0/.stamp_built] Error 2
> make[1]: *** [Makefile:82: _all] Error 2
> make: *** [Makefile:106: /src/linux-bsp-stm32mp133c/output/development/host/bin/arm-none-linux-gnueabihf-gcc] Error 2
This error log is unfortunately useless, as you didn't copy/paste
enough of the build log to have the actual error. All we can see from
this is that the compilation failed during the host-gcc-final step.
Please provide:
1. A Buildroot .config file that allows to reproduce the issue with
upstream Buildroot (without any custom changes)
2. The full build log, preferably posted on some pastebin site, as the
mailing list will not accept a mail that contains a full build log.
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 20:10 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 [this message]
2024-07-17 21:33 ` Florian Fainelli
2024-07-17 21:53 ` Thomas Petazzoni via buildroot
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=20240717221000.5ced2d0d@windsurf \
--to=buildroot@buildroot.org \
--cc=Murali.Karicheri@sandc.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