On 3/2/26 4:28 PM, Javier Martinez wrote: > Call it as you prefer, Most users will not change default std. > Do you prefer gcc 15 is more strict because "by default" it uses one std > sintactically stricter? > > I got realize about this because hiawatha failed compiling with gcc 15 > working with gcc 14 by minor syntax changes. Because of this I suggest > him to change his compiler. Of course my solution is just a hack, a > workaround, until developers port to the stricter syntax. > > Of course, my english is also horrible so I could explain him how to > make a cup of coffee instead of how to do a workaround...
There is an important distinction to make: adding -std=gnu17 to CFLAGS inside the ebuild will allow building with newer gcc, and this is a standard, acceptable / QA compliant way to fix a package without revbumping. That means e.g. if you depcleaned old gcc already you need not feel required to go build it again just for some non-c23 compatible package. (Don't add it to make.conf, this can break packages that already set it to something lower. Using package.env could work while waiting for ::gentoo to include it in the ebuild, I guess.) e.g. grep the gentoo repo for `append-cflags -std=gnu17` (It is always best to report upstream so they can either be c23-compatible or explicitly specify the std they use! But that is separate from getting the ::gentoo ebuild to compile.) -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
