<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/glibc.git/support, branch master</title>
<subtitle>GNU C Library
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/glibc.git/atom?h=master</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/'/>
<updated>2026-03-12T16:52:50Z</updated>
<entry>
<title>configure: Repurpose have-cc-with-libunwind for clang support</title>
<updated>2026-03-12T16:52:50Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2026-02-25T18:31:14Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=570c46d36bc9123597a601e500d9d7661d71247b'/>
<id>urn:sha1:570c46d36bc9123597a601e500d9d7661d71247b</id>
<content type='text'>
The `have-cc-with-libunwind` check (and its corresponding macro
HAVE_CC_WITH_LIBUNWIND) was historically specific to IA64, intended
to supplement libgcc with libunwind.  Since this logic is unused in
current GCC configurations, this patch repurposes it to support
clang-based toolchains that utilize LLVM's libunwind instead of
libgcc_s.

The configure script now detects if the compiler natively supports
unwinding via `-lunwind`.

Additionally, when this mode is enabled, `-lclang_rt.builtins` is
explicitly added to the `libgcc_eh` definition.  This is necessary
because `links-dso-program` otherwise fails to link due to a missing
`__gcc_personality_v0` symbol.  It appears that clang does not
automatically link the builtins providing this personality routine
when `rlink-path` is actively used during the build.

Reviewed-by: Sam James &lt;sam@gentoo.org&gt;
</content>
</entry>
<entry>
<title>configure: Parametrize runtime libraries to support compiler-rt</title>
<updated>2026-03-12T16:52:50Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2026-02-25T18:31:13Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=79942df7c5ceae3468dd15af61bba288447ffe9f'/>
<id>urn:sha1:79942df7c5ceae3468dd15af61bba288447ffe9f</id>
<content type='text'>
Historically, the build system has hardcoded references to `-lgcc` and
`-lgcc_eh`, explicitly assuming the use of the GCC runtime.  This
prevents building glibc with alternative toolchains, specifically clang
configured with `--rtlib=compiler-rt`, where these libraries are
replaced by `libclang_rt.builtins`.

This patch introduces a mechanism to dynamically detect the compiler's
underlying runtime library.

The logic works as follows:

1. It queries the compiler using `-print-libgcc-file-name`.
2. It parses the output path to determine if `libgcc` or `compiler-rt`
   is in use.
3. Based on this detection, it parametrizes the build variables for
   the static runtime and exception handling libraries (replacing
   hardcoded `-lgcc` and `-lgcc_eh`).

This ensures that the build system correctly links against the active
compiler runtime—whether it is the traditional libgcc or LLVM's
compiler-rt—without requiring manual overrides.

Reviewed-by: Sam James &lt;sam@gentoo.org&gt;
</content>
</entry>
<entry>
<title>support: no_override_resolv_conf_search flag for resolver test framework</title>
<updated>2026-03-03T17:48:47Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-03-03T17:48:47Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=c995686e2cbe2a3ab2a11877a61c14a2e1fc35cb'/>
<id>urn:sha1:c995686e2cbe2a3ab2a11877a61c14a2e1fc35cb</id>
<content type='text'>
It is required to test "search ." in /etc/resolv.conf files.  The
default is to override the search path isolate from unexpected
settings in the test execution environment.

Reviewed-by: Carlos O'Donell &lt;carlos@redhat.com&gt;
</content>
</entry>
<entry>
<title>support: Add support for starting and stopping nscd</title>
<updated>2026-02-12T11:18:54Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-02-12T11:18:54Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=bba1920c8b20176986ee294d74cef404027d99e8'/>
<id>urn:sha1:bba1920c8b20176986ee294d74cef404027d99e8</id>
<content type='text'>
Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>support: Add missing NSS formatting and checking functions</title>
<updated>2026-02-12T11:18:54Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-02-12T11:18:54Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=c9c4ff0b77d72fa0c1229ac9c52ef42379b1f5a5'/>
<id>urn:sha1:c9c4ff0b77d72fa0c1229ac9c52ef42379b1f5a5</id>
<content type='text'>
This change is largely auto-generated.  The function implementations
are mechanical and use the glibc-specific support framework, so this
should be low-risk and therefore acceptable.

The struct etherent type is currently internal-only (although it
can be used by NSS modules), which is why it is not included here.

Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>support: Clean up NSS formatting and checking functions</title>
<updated>2026-02-12T11:18:54Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-02-12T11:18:54Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=a1a730b0119a5b35dfa59c70c6744246ac1ee7fa'/>
<id>urn:sha1:a1a730b0119a5b35dfa59c70c6744246ac1ee7fa</id>
<content type='text'>
Move &lt;netdb.h&gt; includes into the implementation files.  Use const
where appropriate.  Introduce support_check_nss and use it to
implement the check_* functions.

Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>support: Also put libaudit, libcap into the testroot if present</title>
<updated>2026-02-04T08:46:07Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-02-04T08:46:07Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=fff40098b0716bdd5b1dcd848ff25a2da6c33be2'/>
<id>urn:sha1:fff40098b0716bdd5b1dcd848ff25a2da6c33be2</id>
<content type='text'>
Some configurations of nscd are linked against those libraries.
</content>
</entry>
<entry>
<title>support: Add support_spawn_wrap and related functionality</title>
<updated>2026-02-02T20:15:48Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-02-02T20:15:48Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=229f65f5f322609283c7104c80c8af6434dff628'/>
<id>urn:sha1:229f65f5f322609283c7104c80c8af6434dff628</id>
<content type='text'>
It allows us to write test cases in C that run tests with
dynamic linker wrapping.

The iconv test case was auto-generated.  The posix_spawn usage
is mechanical, and the interface it tests is newly added in this
commit, so this should be acceptable.

Reviewed-by: Adhemerval Zanella &lt;adhemerval.zanella@linaro.org&gt;
</content>
</entry>
<entry>
<title>support: Reinitialize containers if /etc is present</title>
<updated>2026-01-24T09:29:39Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-01-24T09:29:39Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=458a6a2b935f60a25a136846fe8b7a4723296dda'/>
<id>urn:sha1:458a6a2b935f60a25a136846fe8b7a4723296dda</id>
<content type='text'>
This prevents test failures because configuration file leftovers
unexpectedly change glibc for future tests.  Whether this
triggers depends on test execution order.

Adding postclean.req files manually (before this change) appears
too error-prone.

Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>support: Add support_hardcoded_paths_in_test</title>
<updated>2026-01-24T09:29:22Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2026-01-24T09:29:22Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/glibc.git/commit/?id=e8502182f09211663c1583960442eb6ff502a33e'/>
<id>urn:sha1:e8502182f09211663c1583960442eb6ff502a33e</id>
<content type='text'>
It indicates whether glibc was configured with
--enable-hardcoded-path-in-tests.

Reviewed-by: Adhemerval Zanella  &lt;adhemerval.zanella@linaro.org&gt;
</content>
</entry>
</feed>
