<feed xmlns='http://www.w3.org/2005/Atom'>
<title>glibc/configure, branch master</title>
<subtitle>Fork of glibc for development</subtitle>
<id>https://git.zx2c4.com/glibc/atom/configure?h=master</id>
<link rel='self' href='https://git.zx2c4.com/glibc/atom/configure?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/'/>
<updated>2024-07-09T09:54:29Z</updated>
<entry>
<title>manual: add syscalls</title>
<updated>2024-07-09T09:54:29Z</updated>
<author>
<name>DJ Delorie</name>
<email>dj@redhat.com</email>
</author>
<published>2024-07-08T21:52:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=6c0be74305745c8f78bcfb69442c8c379459d99b'/>
<id>urn:sha1:6c0be74305745c8f78bcfb69442c8c379459d99b</id>
<content type='text'>
The purpose of this patch is to add some system calls that (1) aren't
otherwise documented, and (2) are merely redirected to the kernel, so
can refer to their documentation; and define a standard way of doing
so in the future.  A more detailed explaination of how system calls
are wrapped is added along with reference to the Linux Man-Pages
project.

Default version of man-pages is in configure.ac but can be overridden
by --with-man-pages=X.Y

Reviewed-by: Alejandro Colomar &lt;alx@kernel.org&gt;
</content>
</entry>
<entry>
<title>Add --disable-static-c++-tests option [BZ #31797]</title>
<updated>2024-07-02T07:51:34Z</updated>
<author>
<name>H.J. Lu</name>
<email>hjl.tools@gmail.com</email>
</author>
<published>2024-06-20T22:28:13Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=ba144c179eb12a6aff145582671cbb8b1045c5b9'/>
<id>urn:sha1:ba144c179eb12a6aff145582671cbb8b1045c5b9</id>
<content type='text'>
By default, if the C++ toolchain lacks support for static linking,
configure fails to find the C++ header files and the glibc build fails.
The --disable-static-c++-link-check option allows the glibc build to
finish, but static C++ tests will fail if the C++ toolchain doesn't
have the necessary static C++ libraries which may not be easily installed.
Add --disable-static-c++-tests option to skip the static C++ link check
and tests.  This fixes BZ #31797.

Signed-off-by: H.J. Lu &lt;hjl.tools@gmail.com&gt;
</content>
</entry>
<entry>
<title>Add --disable-static-c++-link-check option [BZ #31412]</title>
<updated>2024-07-02T07:51:34Z</updated>
<author>
<name>H.J. Lu</name>
<email>hjl.tools@gmail.com</email>
</author>
<published>2024-06-20T22:28:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=23f12e6e0c95aaf8b5b4973d029db794a43f248a'/>
<id>urn:sha1:23f12e6e0c95aaf8b5b4973d029db794a43f248a</id>
<content type='text'>
The current minimum GCC version of glibc build is GCC 6.2 or newer. But
building i686 glibc with GCC 6.4 on Fedora 40 failed since the C++ header
files couldn't be found which was caused by the static C++ link check
failure due to missing __divmoddi4 which was referenced in i686 libc.a
and added to GCC 7.  Add --disable-static-c++-link-check configure option
to disable the static C++ link test.  The newly built i686 libc.a can be
used by GCC 6.4 to create static C++ tests.  This fixes BZ #31412.

Signed-off-by: H.J. Lu &lt;hjl.tools@gmail.com&gt;
</content>
</entry>
<entry>
<title>Convert to autoconf 2.72 (vanilla release, no distribution patches)</title>
<updated>2024-06-17T19:15:28Z</updated>
<author>
<name>Andreas K. Hüttel</name>
<email>dilfridge@gentoo.org</email>
</author>
<published>2024-06-11T21:34:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=98ffc1bfeb04fb04b7f18f1cbfccf1e43d6a867f'/>
<id>urn:sha1:98ffc1bfeb04fb04b7f18f1cbfccf1e43d6a867f</id>
<content type='text'>
As discussed at the patch review meeting

Signed-off-by: Andreas K. Hüttel &lt;dilfridge@gentoo.org&gt;
Reviewed-by: Simon Chopin &lt;simon.chopin@canonical.com&gt;
</content>
</entry>
<entry>
<title>elf: Enable TLS descriptor tests on aarch64</title>
<updated>2024-03-19T17:53:30Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2024-03-12T16:21:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=3d53d18fc71c5d9ef4773b8bce04d54b80181926'/>
<id>urn:sha1:3d53d18fc71c5d9ef4773b8bce04d54b80181926</id>
<content type='text'>
The aarch64 uses 'trad' for traditional tls and 'desc' for tls
descriptors, but unlike other targets it defaults to 'desc'.  The
gnutls2 configure check does not set aarch64 as an ABI that uses
TLS descriptors, which then disable somes stests.

Also rename the internal machinery fron gnu2 to tls descriptors.

Checked on aarch64-linux-gnu.
Reviewed-by: H.J. Lu &lt;hjl.tools@gmail.com&gt;
</content>
</entry>
<entry>
<title>Ignore undefined symbols for -mtls-dialect=gnu2</title>
<updated>2024-03-19T17:53:30Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2024-03-12T16:21:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=968b0ca9440040a2b31248a572891f0e55c1ab10'/>
<id>urn:sha1:968b0ca9440040a2b31248a572891f0e55c1ab10</id>
<content type='text'>
So it does not fail for arm config that defaults to -mtp=soft (which
issues a call to __aeabi_read_tp).
Reviewed-by: H.J. Lu &lt;hjl.tools@gmail.com&gt;
</content>
</entry>
<entry>
<title>Update copyright dates with scripts/update-copyrights</title>
<updated>2024-01-01T18:53:40Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2024-01-01T18:12:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=dff8da6b3e89b986bb7f6b1ec18cf65d5972e307'/>
<id>urn:sha1:dff8da6b3e89b986bb7f6b1ec18cf65d5972e307</id>
<content type='text'>
</content>
</entry>
<entry>
<title>crypt: Remove libcrypt support</title>
<updated>2023-10-30T16:03:59Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2023-10-02T12:11:49Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=e6e3c666880847ad908692087ca6d5015895dffa'/>
<id>urn:sha1:e6e3c666880847ad908692087ca6d5015895dffa</id>
<content type='text'>
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 &lt;zack@owlfolio.org&gt;
Reviewed-by: Carlos O'Donell &lt;carlos@redhat.com&gt;
</content>
</entry>
<entry>
<title>configure: Remove --enable-all-warnings option</title>
<updated>2023-08-01T18:35:25Z</updated>
<author>
<name>Adhemerval Zanella Netto</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2023-07-24T17:22:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=78ceef25d64efeeb6067d1cb282a00466e637e2a'/>
<id>urn:sha1:78ceef25d64efeeb6067d1cb282a00466e637e2a</id>
<content type='text'>
The option is not activelly tested and has bitrotten, to fix it
would require a lot of work and multiple fixes.  A better option
would to evaluate each option and enable the warning if it makes
sense.
Reviewed-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
</content>
</entry>
<entry>
<title>scripts: Fix fortify checks if compiler does not support _FORTIFY_SOURCE=3</title>
<updated>2023-07-20T20:58:26Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2023-07-20T14:35:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=a3090c2c98facbab3d47aa23a94f8d2caeb78d71'/>
<id>urn:sha1:a3090c2c98facbab3d47aa23a94f8d2caeb78d71</id>
<content type='text'>
The 30379efad1 added _FORTIFY_SOURCE checks without check if compiler
does support all used fortify levels.  This patch fixes it by first
checking at configure time the maximum support fortify level and using
it instead of a pre-defined one.

Checked on x86_64 with gcc 11, 12, and 13.

Reviewed-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
Tested-by: Florian Weimer &lt;fweimer@redhat.com&gt;
</content>
</entry>
</feed>
