This recipe takes longer time >20min when bitbake for package
write stage. When cross-verified for longer time duration, found
that do_check() stage taking 20min while other stages completes
before 6min.
This recipe gives only below two test binaries in the packages to
test (ptest: glibc-y2038-tests):
io/ftwtest
io/ftwtest-time64
The above test binaries are already included for testing in recipe
glibc-testsuite_2.41.bb.
It is by now well established that glibc itself works as it should,
that all affected 32 bit targets are configured to use 64 bit time_t,
and that any lingering y2038 issues are in components other than the c
library, and usually come from C programming mistakes (e.g. storing
timestamps in long). Maybe we can simply remove the recipe?
Review comments for fixing above longer time duration ended up in
removing this recipe as a proposal is below
https://lists.openembedded.org/g/openembedded-core/topic/112188476#msg214636
Removed lines having reference to glibc-y2038-tests in the files.
(From OE-Core rev: fbe3679ba3c12c52a502511f5dde91fb4de7a6b6)
Signed-off-by: rajmohan r <semc.2042@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The original commit incorrectly missed off the pn- override prefix, fix it.
(From OE-Core rev: 766ebeec6fa56305606df3dcf901053dd58c1a95)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pseudo has to wrap all glibc calls including the 32 bit ones so
this warning is a false positive.
(From OE-Core rev: 13f8b50f055be219aed50c62c5f7552c4c2f18f2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GDB 15.2 brings the following fixes:
* PR gdb/31727 (-exec-next fails in mingw (infrun.c:2794: internal-error: resume_1: Assertion `pc_in_thread_step_range (pc, tp)' failed))
* PR c++/31900 (libstdc++-prettyprinters/debug.cc print redirected fails since gdb-14-branchpoint-2123-g4e417d7bb1c)
* PR python/31946 (sys.exit from Python no longer exits the GDB process)
* PR record/31971 (Loading a saved record file asserts if we try to execute the inferior)
* PR gdb/32005 (frv_current_sos doesn't set solib::lm_info)
* PR exp/32015 (GDB crashes while printing large D array)
* PR gdb/32025 (Fatal error when the disassemble command is interrupted with SIGINT)
* PR gdb/32143 ([15 Regression] arch/amd64.c:71: internal-error: amd64_create_target_description: Assertion `!is_x32' failed)
* PR symtab/32158 ([gdb/symtab] enum class enumerator has incorrect parent in cooked index)
* PR symtab/32160 ([gdb/symtab] Parent map: die parent or scope parent?)
(From OE-Core rev: 76567e7a0e1d133b5878a0254a9dcc87b3a15bc1)
Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The implementation uses the append operator to include
GLIBC_64BIT_TIME_FLAGS in TARGET_CC_ARCH, but it places the space in
the GLIBC_64BIT_TIME_FLAGS assignment in order to avoid a 'spurious
space' when the value is empty.
68b50d3 time64: Remove leading whitespace from GLIBC_64BIT_TIME_FLAGS
The problem with this is it requires anyone wishing to assign a value
to GLIBC_64BIT_TIME_FLAGS to add the leading space, otherwise this is
the error:
cc1: error: '-Werror=format-security-D_TIME_BITS=64': no option '-Wformat-security-D_TIME_BITS=64'
Add a new constant variable to capture the value needed for the 32-bit
special case, including the space.
(From OE-Core rev: e8177827f92e71c80c5b63453d8bbd1defbe1fbc)
Signed-off-by: Tom Hochstein <tom.hochstein@oss.nxp.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixing our infrastructure to show warnings for nativesdk packages resulted
in some issues with 32 bit toolchains and 32 bit time becoming clear.
For now, add INSANE_SKIP entries for these which effectively documents
the issue and allows us to at least start running the tests in the
infrastructure.
Over time we will need to try and fix these if upstream doesn't.
(From OE-Core rev: d05fa366ebbf8017f5f5fae0b1bc8502ada3ab79)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pulseaudio OSS (Open Sound System) support was causing build issues when
used with GLIBC_64BIT_TIME_FLAGS. However, optional OSS support was
disabled by default with addition of PACKAGECONFIG[oss-output]. Thus
remove pulseaudio from the exception list in time64.inc and allow it to
be Y2038 compatible.
(From OE-Core rev: 67cbec2aa1e7dca1abacf39a22efe85fa47a468d)
Signed-off-by: Primoz Fiser <primoz.fiser@norik.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recipe originates from meta-y2038 where the name was not
confusing, but in oe-core it is.
(From OE-Core rev: 90bc7a66b08580207839fc6aafe1ac86c12981c5)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Additionally:
- drop pseudo from INSANE_SKIP for 32bit time API check
(pseudo passes the check; it's not clear where the issue may have been)
- move rust exceptions to the cargo class, as the problem
is common across the ecosystem, and needs to be fixed in the
libc crate.
(From OE-Core rev: d3d406bf636e579c17708b408e11c12d252533ee)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Until strace can handle the interface with glibc correctly with those flags,
disable there for now.
(From OE-Core rev: 5235ae1a14b71d42c1effff51e0289654bc7122a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Existing implementation required to list both specific problematic apis, and files that
use them: neither is necessary as both are seen in package_qa error messages, and
can cause excessive amount of exception lines, if there are too many files, or
they are installed in arch-specific locations. Also, the value of INSANE_SKIP
should be the test that needs to be skipped, and in this case it wasn't.
Also, all problematic recipes are now correctly listed.
(From OE-Core rev: e6ebd0c556dfc576a59f5755d97089a2a241f698)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It builds glibc source like other glibc recipes do,
and so the same problems occur.
(From OE-Core rev: 68b50d362ec61f27be818e40fcbb281d9bacf756)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This avoids adding a spurious space in TARGET_CC_ARCH when
GLIBC_64BIT_TIME_FLAGS is empty
(From OE-Core rev: 5d077129d8e849ce3a79285825231c642e79be70)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It needs to be fixed to honor _FILE_OFFSET_BITS before we can enable
64bit time_t
(From OE-Core rev: 206ab9522963aee471004d987181ed2f8363f1ad)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I meant to do this whilst merging but messed up the patches. This
file is a .inc file and should match the others.
(From OE-Core rev: d9398dfb0866a5be9ed09ae15902606fe11da2d2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
