@thindil
1. This doesn't affect the public #ABI of the kernel. Do you have any example of breakage here? 🤔 Don't get me wrong, I'm really not a fan of the chaos GNU/Linux actually is, but this is still hard to believe.
2. Possible. I don't know any example though ....

Regarding the "standard" #libc, if we're talking about "GNU/Linux", this will always be #glibc. AFAIK, any #Linuxulator userland ever shipped in #FreeBSD ports used it. I plan to do the same trying to build this mess from source 😂

BTW, my "lxcross-glibc" package seems to work, and it seems I'm able to build some *almost* complete cross #GCC using it right now ... still need the --disable-libsanitizer configure flag 🤔

@bitpirate @gamingonlinux and as much as I'd love to see every game getting updated, it's illusional that publishers and devs will invest the time to do so on one-time-purchase titles that are over 2 years old, don't sell any significant numbers or don't get any other revenue to pay for workarounding the shit that #flibc does.

Other #libc's like #musl don't do that.

@lunaa @yura @torvalds I know...

There's a reason Distros like #AlpineLinux, #ChimeraLinux and almost all #embedded systems using #Busybox or #Toybox want to get rid of #glibc if not replace it with something like #uClinux, #musl,or another #libc...

Because glibc bricking stuff with minor updates kills any #CCSS and any non-#FLOSS that can't be recompiled.

And what RMS et. al. may see as intentional, I think is the biggest issie that prevents #Linux from dominating #Desktop|s!

It's one of those weeks where debugging a single core dump on #OracleSolaris leads to making fixes in both #gdm & #libc:

https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/213

@dbanty #Musl binaries won't use any facilities unique to #glibc, most notably the Name Service Switch (NSS).

The deal with glibc is that you have to compile against the oldest version of glibc you're willing to support. Versions older than the one you compiled against are unlikely to work. That's fine if you're a distro maintainer or building for your own use, but can be a problem when distributing binaries.

Lucky for you, Rust makes it trivial to choose which #libc you want to use.

[A] review of the C standard library in practice, https://nullprogram.com/blog/2023/02/11/.

All the numerous dangers of the standard libc. The article reviews many surfaces of the API and explains why they are misused in most of the case.

#api #c #library #libc

PcapPlusPlus, la lib C++ incontournable pour les amateurs de paquets réseaux https://korben.info/pcaplusplus-bibliotheque-capture-analyse-forgeage-paquets-reseau-protocoles.html #bibliothèqueC++ #Développement #PcapPlusPlus #paquets #réseaux #WinPcap #libC++

I was looking at the 'Blinkenlights' project by Justine Tunney which is "a virtual machine that runs statically-compiled x86-64-linux programs on different operating systems and hardware architectures" (might as well let Justine describe it!) motivated by research on APE ("Actually Portable Executable")¹ ². #ActuallyPortableExecutable

After appreciating blink I looked at Justine's other repos, as one does, and… here's what I already bookmarked:

* "sectorlisp is a 512-byte implementation of LISP that's able to bootstrap John McCarthy's meta-circular evaluator on bare metal." - https://github.com/jart/sectorlisp #Lisp

* "Cosmopolitan Libc makes C a build-once run-anywhere language, like Java, except it doesn't need an interpreter or virtual machine. Instead, it reconfigures stock GCC and Clang to output a POSIX-approved polyglot format that runs natively on Linux + Mac + Windows + FreeBSD + OpenBSD + NetBSD + BIOS with the best possible performance and the tiniest footprint imaginable." - https://github.com/jart/cosmopolitan #Libc #VirtualMachine #Polyglot (you should also look at the work by @Ange on the vast subject of polyglots)

* "Disaster lets you press C-c d to see the compiled assembly code for the C, C++ or Fortran file you're currently editing. It even jumps to and highlights the line of assembly corresponding to the line beneath your cursor." - https://github.com/jart/disaster #Emacs #EmacsLisp #Disassembler ( @anticomputer this one is for you…)

No apologies for sending you down this Github hole :flan_molotov:​ as it is more fun to go spelunking with friends!

__
¹ https://justine.lol/ape.html
² https://github.com/jart/blink

#unix #libc #networking

It's very annoying that #ISO #C has fixed-width integer types in stdint.h, but doesn't provide #libc functions for working with them, like for instance, strtoi32(). Heck, standard C doesn't even have strtoint() for regular ints!

the closest I've come is strtoi() which lets you specify bounds, so you could use E.G. INT32_MIN & INT32_MAX, but that's a nonstandard #BSD extension.

So you have to use a bunch of macro soup to fix this problem yourself and use strtoimax(), which defeats the entire point of the stdint types. 😤

Pretty Petite Picolibc Powers Processors https://hackaday.com/2022/11/14/pretty-petite-picolibc-powers-processors/ #SoftwareDevelopment #Microcontrollers #standardlibrary #newlib #libc

Pretty Petite Picolibc Powers Processors - Many times when someone tells you that language X is “better” at something they re... - https://hackaday.com/2022/11/14/pretty-petite-picolibc-powers-processors/ #softwaredevelopment #microcontrollers #standardlibrary #newlib #libc

Pretty Petite Picolibc Powers Processors

https://hackaday.com/2022/11/14/pretty-petite-picolibc-powers-processors/

#SoftwareDevelopment #Microcontrollers #standardlibrary #newlib #libc

One of my frustrations with #macOS is that it has a broken wcwidth (a #libc function that gets the column width of a wide char).

It thinks each decomposed part of the character '국' (total 2 colums wide) is at least 1 column wide, hence thinking that the whole string needs 4 columns! (Left is the broken macOS, right is the correct Ubuntu.)

This wrecks the #shell line editor, and if I complete a Korean file name, I lose my cursor and the terminal starts erasing wrong characters. So frustrating…

One of my frustrations with #macOS is that it has a broken wcwidth (a #libc function that gets the column width of a wide char).

It thinks each decomposed part of the character '국' (total 2 colums wide) is at least 1 column wide, hence thinking that the whole string needs 4 columns! (Left is the broken macOS, right is the correct Ubuntu.)

This wrecks the #shell line editor, and if I complete a Korean file name, I lose my cursor and the terminal starts erasing wrong characters. So frustrating…

https://fosdem.org/2022/schedule/event/llvm_oniro/# #Oniro 3rd presentation for today is starting soon at 15h35 CET:
#Libc++ on #Linux - using the example of #Oniro
Experiences with switching from #libstdc++ to #libc++
Join
bero in
#LLVM devroom and then stay longer in room for Q&A
https://fosdem.org/2022/schedule/event/llvm_oniro/

Linux Standard Library Implementations: X32 can be 10% faster, but musl Libc 40% slower: https://www.youtube.com/watch?v=wq-a8juPFzs #linux #glibc #musl #libc #performance #comparison #standardlibrary #x32