<feed xmlns='http://www.w3.org/2005/Atom'>
<title>glibc/scripts, branch glibc-2.38</title>
<subtitle>Fork of glibc for development</subtitle>
<id>https://git.zx2c4.com/glibc/atom/scripts?h=glibc-2.38</id>
<link rel='self' href='https://git.zx2c4.com/glibc/atom/scripts?h=glibc-2.38'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/'/>
<updated>2023-07-20T20:58:26Z</updated>
<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>
<entry>
<title>configure: Disable building libcrypt by default</title>
<updated>2023-07-20T18:38:13Z</updated>
<author>
<name>Siddhesh Poyarekar</name>
<email>siddhesh@sourceware.org</email>
</author>
<published>2023-07-17T16:44:17Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=6c85c5a1773d786ccdc375e34431488fbcdd88e0'/>
<id>urn:sha1:6c85c5a1773d786ccdc375e34431488fbcdd88e0</id>
<content type='text'>
We mentioned eventual dropping of libcrypt in the 2.28 NEWS.  Actually
put that plan in motion by first disabling building libcrypt by default.
note in NEWS that the library will be dropped completely in a future
release.

Also add a couple of builds into build-many-glibcs.py.

Signed-off-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
Reviewed-by: Andreas K. Hüttel &lt;dilfridge@gentoo.org&gt;
</content>
</entry>
<entry>
<title>scripts: Add fortify checks on installed headers</title>
<updated>2023-07-19T19:06:24Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2023-07-19T14:37:01Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=30379efad117b85cc56a255cac628d0ad745bfe3'/>
<id>urn:sha1:30379efad117b85cc56a255cac628d0ad745bfe3</id>
<content type='text'>
The _FORTIFY_SOURCE is used as default by some system compilers,
and there is no way to check if some fortify extension does not
trigger any conformance issue.

Checked on x86_64-linux-gnu.

Reviewed-by: Carlos O'Donell &lt;carlos@redhat.com&gt;
</content>
</entry>
<entry>
<title>Allow glibc to be built with _FORTIFY_SOURCE</title>
<updated>2023-07-05T14:59:34Z</updated>
<author>
<name>Frédéric Bérat</name>
<email>fberat@redhat.com</email>
</author>
<published>2023-03-17T09:14:50Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=64d9580cdf7e417170abbef0327e04b29712e949'/>
<id>urn:sha1:64d9580cdf7e417170abbef0327e04b29712e949</id>
<content type='text'>
Add --enable-fortify-source option.

It is now possible to enable fortification through a configure option.
The level may be given as parameter, if none is provided, the configure
script will determine what is the highest level possible that can be set
considering GCC built-ins availability and set it.
If level is explicitly set to 3, configure checks if the compiler
supports the built-in function necessary for it or raise an error if it
isn't.

If the configure option isn't explicitly enabled, it _FORTIFY_SOURCE is
forcibly undefined (and therefore disabled).

The result of the configure checks are new variables, ${fortify_source}
and ${no_fortify_source} that can be used to appropriately populate
CFLAGS.

A dedicated patch will follow to make use of this variable in Makefiles
when necessary.

Updated NEWS and INSTALL.

Adding dedicated x86_64 variant that enables the configuration.

Reviewed-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
</content>
</entry>
<entry>
<title>Use Linux 6.4 in build-many-glibcs.py</title>
<updated>2023-06-27T13:49:38Z</updated>
<author>
<name>Joseph Myers</name>
<email>joseph@codesourcery.com</email>
</author>
<published>2023-06-27T13:49:38Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=aaa208502c97707119aea9e03a988bec26ad7817'/>
<id>urn:sha1:aaa208502c97707119aea9e03a988bec26ad7817</id>
<content type='text'>
This patch makes build-many-glibcs.py use Linux 6.4.

Tested with build-many-glibcs.py (host-libraries, compilers and glibcs
builds).
</content>
</entry>
<entry>
<title>Add lint-makefiles Makefile linting test.</title>
<updated>2023-06-03T01:43:05Z</updated>
<author>
<name>Carlos O'Donell</name>
<email>carlos@redhat.com</email>
</author>
<published>2023-05-18T20:18:22Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=547de57e5a54d3a02733523b75f261e95fc71579'/>
<id>urn:sha1:547de57e5a54d3a02733523b75f261e95fc71579</id>
<content type='text'>
We add a 'make check' test that lints all Makefiles in the source
directory of the glibc build. This linting test ensures that the
lines in all Makefiles will be sorted correctly as developers
creates patches.  It is added to 'make check' because it is
light-weight and supports the existing developer workflow

The test adds ~3s to a 'make check' execution.

No regressions on x86_64 and i686.

Reviewed-by: Florian Weimer &lt;fweimer@redhat.com&gt;
</content>
</entry>
<entry>
<title>Fix a few more typos I missed in previous round -- BZ 25337</title>
<updated>2023-06-02T23:46:32Z</updated>
<author>
<name>Paul Pluzhnikov</name>
<email>ppluzhnikov@google.com</email>
</author>
<published>2023-06-02T03:40:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=2cbeda847bb58bfac73d2048e3e0300ff1b2b894'/>
<id>urn:sha1:2cbeda847bb58bfac73d2048e3e0300ff1b2b894</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix all the remaining misspellings -- BZ 25337</title>
<updated>2023-06-02T01:39:48Z</updated>
<author>
<name>Paul Pluzhnikov</name>
<email>ppluzhnikov@google.com</email>
</author>
<published>2023-05-20T13:37:47Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=7f0d9e61f40c669fca3cfd1e342fa8236c7220b7'/>
<id>urn:sha1:7f0d9e61f40c669fca3cfd1e342fa8236c7220b7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>scripts: sort-makefile-lines.py</title>
<updated>2023-05-18T16:33:24Z</updated>
<author>
<name>Carlos O'Donell</name>
<email>carlos@redhat.com</email>
</author>
<published>2023-05-17T13:16:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=b0528456a606faf996ae8046512d623a6d22d0cc'/>
<id>urn:sha1:b0528456a606faf996ae8046512d623a6d22d0cc</id>
<content type='text'>
We must return &lt; 0, 0, or &gt; 0 as the result of the comparison function
for cmp_to_key() to work correctly across all comparisons.

Reviewed-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
</content>
</entry>
<entry>
<title>scripts: Add sort-makefile-lines.py to sort Makefile variables.</title>
<updated>2023-05-10T17:14:52Z</updated>
<author>
<name>Carlos O'Donell</name>
<email>carlos@redhat.com</email>
</author>
<published>2023-04-18T15:02:55Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=1270549a267eb4c8b8dda7fd9a91d7f14968d58f'/>
<id>urn:sha1:1270549a267eb4c8b8dda7fd9a91d7f14968d58f</id>
<content type='text'>
The scripts/sort-makefile-lines.py script sorts Makefile variables
according to project expected order.

The script can be used like this:

$ scripts/sort-makefile-lines.py &lt; elf/Makefile &gt; elf/Makefile.tmp
$ mv elf/Makefile.tmp elf/Makefile

Reviewed-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
</content>
</entry>
</feed>
