Conversation

Notices

1. Embed this notice
   翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Friday, 02-Jan-2026 19:41:29 JST 翠星石

   • Wolf480pl
   @wolf480pl >Linux system
   equery b ld-linux-x86-64.so.2
   sys-libs/glibc-2.42 (/lib64/ld-linux-x86-64.so.2)
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Friday, 02-Jan-2026 19:45:12 JST 翠星石

     in reply to

     • Wolf480pl
     @wolf480pl You could have just written x86-64 GNU system and have been correct and have saved yourself some typing.
   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Friday, 02-Jan-2026 19:45:13 JST Wolf480pl

     in reply to

     @Suiseiseki I meant "x86-64 glibc Linux system" but it autocorrected "glibc" to "going" :blobfacepalm:

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Friday, 02-Jan-2026 19:58:24 JST 翠星石

     in reply to

     • Wolf480pl
     @wolf480pl On GNU/Hurd it's just /lib/ld.so.1
   • Embed this notice
     Wolf480pl (wolf480pl@mstdn.io)'s status on Friday, 02-Jan-2026 19:58:25 JST Wolf480pl

     in reply to

     @Suiseiseki
     are you sure glibc puts the dynamic linker at the same path regardless if it's built for Linux, HURD, or kFreeBSD? And on all these systems, the path contains the word "linux"?

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Friday, 02-Jan-2026 19:58:25 JST 翠星石

     in reply to

     • Wolf480pl
     @wolf480pl Okay, I guess "x86-64 GNU/Linux system" would have been needed to be specific enough.