• Release
• 2.41

Release/2.41

1. Current status

On master branch, glibc-2.41 is currently under development and planned for release on 2025-02-01.

The release branch of glibc-X.Y is/will be maintained by USER (USER@EMAIL) tagged on DATE.

The ref structure of this branch is:

• release/2.41/master: Rolling release main branch

These people are interested in contents and further revisions tagged on the branch:

• PERSON1
• PERSON2
• ...

The general policies for release branches apply to this branch. Do you think a certain bugfix should be included in this branch?

1. Is the fix committed in master? It has to be, unless it's not applicable to master (e.g. code has been rewritten meantime).
2. Do you have commit permissions? If so, go ahead if you think it's reasonably safe. break;
3. Can you handle Git yourself? Then you can clone the glibc repository, cherry-pick the appropriate fixes, push your branch out and send a pull request at libc-alpha. break;
4. Add the glibc_X.Y keyword to the appropriate bug report.
5. If there is no appropriate bug report, send a request for the fix to be included to libc-alpha.

The release/X.Y/master branch is intended as a rolling release for all distributions to use and contribute fixes to from development master.

2. Packaging Changes

2.1. Change 1

Describe any distribution packing changes that may be required.

2.2. Change 2

And another change.

3. Planning

What things do we want to accomplish this release?

3.1. Release blockers?

3.2. Desirable this release?

• Review new pthread cancel implementation.

  • Carlos reviewed v7 and v8 in progress.

• Extend Rseq Support

• Improve executable stack handling

• Some DNS stub resolver fixes/enhancements

• Review pthread condvar missing signal bug 25847.

  • Carlos has a test case, but still not done. Can be backported without ABI implications.
• Thread-safe getenv

3.3. Already fixed / merged from above

3.4. Deferred to next release

4. Build and test results

Describe build and test issues for each architecture, or confirm a clean build with no testsuite failures. The list below is not a complete list of ABI variants; testing should try to cover the different ABI variants as far as possible.

Build system:

• Compiler: gcc -v

• Binutils: as -v

• Kernel: uname -a

• Tester: Your Name

• Branch at COMMIT HASH

TRIMMED LIST OF FAILURES.

4.1. AArch64

4.1.1. host 1

4.1.2. host 2

4.2. Alpha

4.3. ARM

4.4. HPPA

4.5. LoongArch (64-bit hard-float)

4.6. LoongArch (64-bit soft-float)

4.7. M68K

4.8. MIPS (32-bit, O32)

4.9. MIPS (64-bit, N32)

4.10. MIPS (64-bit, N64)

4.11. OpenRISC

4.12. PowerPC (32-bit soft-float)

4.13. PowerPC (32-bit hard-float)

4.14. PowerPC (64-bit hard-float)

4.15. PowerPC64LE (64-bit hard-float)

4.16. RISC-V (rv32)

4.17. RISC-V (rv64imac/lp64)

4.18. RISC-V (rv64imafdc/lp64)

4.19. RISC-V (rv64imafdc/lp64d)

4.20. S/390 (32-bit)

4.21. S/390 (64-bit)

4.22. SPARC (32-bit)

4.23. SPARC (64-bit)

4.24. x86 (32-bit, Linux)

4.25. x86_64 (64-bit, Linux)

4.26. x86_64 (x32, Linux)

4.27. x86 (32-bit, Hurd)

4.28. x86_64 (64-bit, Hurd)

5. Additional testing (RM only)

5.1. gnulib test suite

See Testing/Gnulib for details. Build system:

• gcc ...

No regressions compared to ...

.o files:

bla.o
...

Test suite results:

============================================================================
Testsuite summary for dummy 0
============================================================================
# TOTAL: 719
...