Conversation

Notices

1. Embed this notice
   nmeum (nmeum@chaos.social)'s status on Monday, 23-Sep-2024 14:46:22 JST nmeum

   The new enabled-by-default compile errors in GCC 14 can introduce subtle build changes by causing feature test code to no longer compile correctly, thereby breaking feature detection https://github.com/justinethier/cyclone/pull/544

   Noticed this by accident, hope this wasn't a common occurrence during GCC 14 rebuilds.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 23-Sep-2024 14:46:21 JST Haelwenn /элвэн/ :triskell:

     in reply to

     @nmeum Which is a pretty big reason why compiler errors shouldn't be hidden, or worse sent to /dev/null like here so you can't even check something like config.log for known problems.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 23-Sep-2024 15:59:05 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @nmeum Well some automation can be done, like gentoo checks the config.log since gcc10 and warns if it found possible problems.
   • Embed this notice
     nmeum (nmeum@chaos.social)'s status on Monday, 23-Sep-2024 15:59:06 JST nmeum

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan Right, totally agree, but even then you still need someone to actually check the config.log file manually.