Assigning your copyright to the FSF helps defend the GPL and keep software free. Thank you Vivien Kraus for assigning your copyright to the FSF! More at: https://u.fsf.org/463 #glibc #GNULib #CopyrightAssignments

Le Patch progresse, j’en suis à la révision 19 (première version fin mai dernier lol) donc on peut dire que c’est un travail de longue haleine. Mais avec un peu de chance, on va y arriver :nod:

Pour rappel, il s’agit de faire en sorte que les arguments de la ligne de commande soient traduits.

$ myprogram --entrée=fichier.txt --sortie=résultat.txt

https://patchwork.sourceware.org/project/glibc/list/?series=55215

#glibc #i18n

Postman fails to start #2204 #lts #glibc

https://askubuntu.com/q/1560325/612

Assigning your copyright to the FSF helps defend the GPL and keep software free. Thank you Vivien Kraus for assigning your copyright to the FSF! More at: https://u.fsf.org/463 #glibc #GNULib #CopyrightAssignments

Assigning your copyright to the FSF helps defend the GPL and keep software free. Thank you Vivien Kraus for assigning your copyright to the FSF! More at: https://u.fsf.org/463 #glibc #GNULib #CopyrightAssignments

La révision 18 du patch est prête ! Malheureusement, les patches ont été reçus dans le désordre donc ça perturbe Patchwork.
De façon plus globale, j’y crois de plus en plus.
https://patchwork.sourceware.org/project/glibc/list/?series=54642

#glibc #getopt #i18n

systemd führt experimentelle Unterstützung für musl libc ein
https://linuxnews.de/systemd-fuehrt-experimentelle-unterstuetzung-fuer-musl-libc-ein/ #systemd #glibc # musl #linux #linuxnews

Assigning your copyright to the FSF helps defend the GPL and keep software free. Thank you Vivien Kraus for assigning your copyright to the FSF! More at: https://u.fsf.org/463 #glibc #GNULib #CopyrightAssignments

Assigning your copyright to the FSF helps defend the GPL and keep software free. Thank you Vivien Kraus for assigning your copyright to the FSF! More at: https://u.fsf.org/463 #glibc #GNULib #CopyrightAssignments

Assigning your copyright to the FSF helps defend the GPL and keep software free. Thank you Vivien Kraus for assigning your copyright to the FSF! More at: https://u.fsf.org/463 #glibc #GNULib #CopyrightAssignments

Коробка багов (взрывается): кроссплатформенное коварство

В сентябре мы рассматривали релиз 86Box v5.0, приуроченный к тридцати годам со дня выхода в розничную продажу Windows 95, и пообещали показать ещё кое-что. О чём мы сознательно умолчали, и почему оставили находку для отдельной статьи? Что осталось в "коробке"?

https://habr.com/ru/companies/pvs-studio/articles/963286/

#pvsstudio #86box #libc #glibc #freebsd #c11 #эмуляция #совершенный_код #стандарты_кодирования

Initial Clang build support for #GLIBC developed by @zatrazz and HJ Lu!

https://sourceware.org/pipermail/libc-alpha/2025-October/171205.html

@llvm @llvm@mastodon.social Celebrating US LLVM Developer Meeting 2025

I am a bit sad my IETF #dnsop post did not generate at least one reply in 2 days. Ok, I put too much text in before the important part. At least my #glibc patches got some comments. Back to ground and focus on issues in sprint instead.

Something convenient I missed in the news whilst preoccupied with world events four years ago:

> In order to support smoother in-place-upgrades and to simplify the implementation of the runtime all functionality formerly implemented in the libraries libpthread, libdl, libutil, libanl has been integrated into libc. New applications do not need to link with -lpthread, -ldl, -lutil, -lanl anymore. For backwards compatibility, empty static archives libpthread.a, libdl.a, libutil.a, libanl.a are provided, so that the linker options keep working.

https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html

#glibc Useful to know when linking #C, #C++, #CPP, #Rust etc

Edited: formatting

🌘 Bazel 與 glibc 版本不符：揭露建構再現性中的隱藏陷阱
➤ 當快取機制遇上系統 ABI 差異：一個關於再現性的警示
✤ https://blogsystem5.substack.com/p/glibc-versions-bazel
本文深入探討了 Bazel 的快取機制、遠端執行與不同 Linux 發行版上 glibc 版本差異所引發的建構再現性問題。作者透過一個實際案例，說明瞭開發者工作站、CI 系統與生產環境間 glibc 版本不一致，如何導致在開發時測試通過、但上線後服務卻因缺少特定 glibc 版本符號而崩潰。文章分析了這個問題的根本原因——C/C++ 建構過程中對系統依賴（特別是 glibc 版本）的隱性連結，而 Bazel 的預設快取鍵卻無法辨識這些差異。最後，作者提出了一種「手動分割 ACL」的臨時解決方案，透過捕獲並將 glibc 版本納入工具鏈，使其成為快取鍵的一部分，以防止這類災難性錯誤。
+ 這個問題很常見，但很少有人能深入分析其根源。感謝作者提出的解決方案！
+ 『The
#建構系統 #C++ #glibc #Bazel #CICD #系統管理

My #glibc bug report turned out to be pretty successful! Not only glibc got a fix, but also a #GCC bug fix was made; all this happened within a week.

Don't hesitate to report a bug when you see one.

#GNU #Linux #OpenSource #Hobbyist

I upgraded to #glibc 2.42 and filed a bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33367

#GCC #GNU #Linux

August’s Tumbleweed updates are great! Kernel 6.16 adds #RaspberryPi 5 RP1 support, #KDE Gear 25.08 improves travel apps & Dolphin, and #glibc 2.42 brings C23 support. Stay secure, stay rolling. https://news.opensuse.org/2025/09/02/tw-monthly-update-august/

@sandro @OS1337 granted, I demand that said Software handles it's dependencies within, cuz I'm sock and tired of #GlibC shenanigans and nonchalant maintainers if it that say 'just recompile it' and 'not my problem if you use non-FLOSS!'...

🌘 dlclose 無法卸載函式庫的原因為何？
➤ 一場關於動態函式庫卸載的偵錯寓言
✤ https://kishoreganesh.com/post/why-dl-close-did-not-work/
作者在工作中遇到一個棘手的問題，當他嘗試卸載動態載入的函式庫時，`dlclose` 並未如預期般將其完全移除。此問題影響了一個 Rust 函式庫 (libA) 及其 C++ 依賴函式庫 (libB)，導致 libB 的初始化失敗，因為它被錯誤地認為已準備就緒。文章深入探討了 `dlclose` 的運作機制，並揭示了 `libstdc++.so` 中的 `STB_GNU_UNIQUE` 符號標記以及函式庫中註冊的執行緒局部儲存 (TLS) 解構器是導致無法卸載的根本原因。作者也分享了透過 `LD_DEBUG` 環境變數和在 `dlclose` 中設定中斷點來進行偵錯的經驗。
+ 真是太詳細的分析了！我之前也遇過類似的函式庫載入問題，但從沒想過 TLS 解構器會是罪魁禍首。
+ 這篇文章的偵錯思路非常值得學習，特別是 `L
#函式庫管理 #動態載入 #C++ #Rust #glibc