Conversation

Notices

1. Embed this notice
   anna (navi@social.vlhl.dev)'s status on Saturday, 20-Jul-2024 10:31:03 JST anna
   pam_openrc.so fails to build on freebsd because one of the functions in misc.c uses environ (more specifically, env_filter, which, uh, needs to do that)
   
   and freebsd does not define a weak symbol in libc for envron, so, that + meson adding `-Wl,--no-undefined` means it just doesn't build
   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Saturday, 20-Jul-2024 10:42:54 JST anna

     in reply to

     https://reviews.freebsd.org/D30842

     dlsym(RTLD_DEFAULT, "environ")

     really freebsd, really? ugh

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 20-Jul-2024 10:48:18 JST Haelwenn /элвэн/ :triskell:

     in reply to

     @navi Reminds me of https://mastodon.social/@andrewrk/112805966960269831

     And also reminds me that I got a bit surprised with POSIX not putting environ in any header but instead pointing at extern char **environ;. (See https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html )

   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Saturday, 20-Jul-2024 10:50:09 JST anna

     in reply to

     what is pissing me off here is the:

     getenv(3) doesn’t return environ, instead it returns individual environment values.

     Is it possible to retrieve the environ value in some other way?

     Why do you need it?

     oh no, a library wanting to loop over the environment is too much, but executables can, i guess?

     Haelwenn /элвэн/ :triskell: likes this.