GNU C Library https://git.stealer.net/cgit.cgi/user/sven/glibc.git/atom?h=master 2026-01-01T21:42:29Z 2026-01-01T21:42:29Z Paul Eggert eggert@cs.ucla.edu 2026-01-01T17:32:02Z urn:sha1:66f3e9219d8f86b977d9be04ad469b5d72af0da2 2025-01-01T19:22:09Z Paul Eggert eggert@cs.ucla.edu 2025-01-01T18:14:45Z urn:sha1:2642002380aafb71a1d3b569b6d7ebeab3284816 2024-10-01T11:44:41Z Adhemerval Zanella adhemerval.zanella@linaro.org 2024-09-10T12:22:19Z urn:sha1:4d8965f1304a205f7580fe23bb2d462828d1f8e5 Even though building glibc with 64 bit time_t flags is not supported, and the usual way is to patch the build system to avoid it; some systems do enable it by default, and it increases the requirements to build glibc in such cases (it also does not help newcomers when trying to build glibc). The conform namespace and linknamespace tests also do not expect that flag to be set by default, so disable it as well. Checked with a build/check for major ABI and some (i386, arm, mipsel, hppa) with a toolchain that has LFS flags by default. Reviewed-by: DJ Delorie <dj@redhat.com> 2024-10-01T11:44:41Z Adhemerval Zanella adhemerval.zanella@linaro.org 2024-09-10T12:22:18Z urn:sha1:3f1932ed2e6b643848ea7a42f9f15ed80552befb Even though building glibc with LFS flags is not supported, and the the usual way is to patch the build system to avoid it [1]; some system do enable it by default, and it increases the requirements to build glibc in such cases (it also does not help newcomers when trying to build glibc). The conform namespace and linknamespace tests also do not expect that flag to be set by default, so disable it as well. Checked with a build/check for major ABI and some (i386, arm, mipsel, hppa) with a toolchain that has LFS flags by default. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=31624 Reviewed-by: DJ Delorie <dj@redhat.com> 2024-02-25T18:38:16Z Carlos O'Donell carlos@redhat.com 2023-06-05T11:14:41Z urn:sha1:06e51f4d6d1f19b55a0b6f4d5031eb0703c369c9 Reflow and sort Makefile. No code changes in generated binary artifacts. No regressions on x86_64 and i686. 2024-01-01T18:53:40Z Paul Eggert eggert@cs.ucla.edu 2024-01-01T18:12:26Z urn:sha1:dff8da6b3e89b986bb7f6b1ec18cf65d5972e307 2023-10-30T16:03:59Z Adhemerval Zanella adhemerval.zanella@linaro.org 2023-10-02T12:11:49Z urn:sha1:e6e3c666880847ad908692087ca6d5015895dffa All the crypt related functions, cryptographic algorithms, and make requirements are removed, with only the exception of md5 implementation which is moved to locale folder since it is required by localedef for integrity protection (libc's locale-reading code does not check these, but localedef does generate them). Besides thec code itself, both internal documentation and the manual is also adjusted. This allows to remove both --enable-crypt and --enable-nss-crypt configure options. Checked with a build for all affected ABIs. Co-authored-by: Zack Weinberg <zack@owlfolio.org> Reviewed-by: Carlos O'Donell <carlos@redhat.com> 2023-01-06T21:14:39Z Joseph Myers joseph@codesourcery.com 2023-01-06T21:08:04Z urn:sha1:6d7e8eda9b85b08f207a6dc6f187e94e4817270f 2022-01-01T19:40:24Z Paul Eggert eggert@cs.ucla.edu 2022-01-01T18:54:23Z urn:sha1:581c785bf31bc74430320c7856bbfa3875d025fe I used these shell commands: ../glibc/scripts/update-copyrights $PWD/../gnulib/build-aux/update-copyright (cd ../glibc && git commit -am"[this commit message]") and then ignored the output, which consisted lines saying "FOO: warning: copyright statement not found" for each of 7061 files FOO. I then removed trailing white space from math/tgmath.h, support/tst-support-open-dev-null-range.c, and sysdeps/x86_64/multiarch/strlen-vec.S, to work around the following obscure pre-commit check failure diagnostics from Savannah. I don't know why I run into these diagnostics whereas others evidently do not. remote: *** 912-#endif remote: *** 913: remote: *** 914- remote: *** error: lines with trailing whitespace found ... remote: *** error: sysdeps/unix/sysv/linux/statx_cp.c: trailing lines 2021-09-17T19:24:14Z Joseph Myers joseph@codesourcery.com 2021-09-17T19:24:14Z urn:sha1:885762aa31d75de8b9fea4c0e2e372b582d4c548 My glibc bot showed that my conformtest changes fail the build of the conformtest execution tests for x86_64-linux-gnu-static-pie, because linking the newly built object with the newly built libc and the associated options normally used for linking requires it to be built as PIE. Add $(pie-default) to the compiler command used so that PIE options are used when required. There's a case for using the whole of $(CFLAGS-.o) (which includes $(pie-default)), but that raises questions of any impact from using optimization flags from CFLAGS in these tests. So for now just use $(pie-default) as the key part of $(CFLAGS-.o) that's definitely needed. Tested with build-many-glibcs.py for x86_64-linux-gnu-static-pie.