Ühel kenal päeval, E, 31.07.2017 kell 21:00, kirjutas Grant Edwards: > On 2017-07-31, Mateusz Lenik <m...@mlen.pl> wrote: > > On Mon, Jul 31, 2017 at 08:02:34PM +0000, Grant Edwards wrote: > > > ../../third_party/vulkan-validation- > > > layers/src/loader/debug_report.c:50:5: > > > note: use option -std=c99, -std=gnu99, -std=c11 or -std=gnu11 to > > > compile your code > > > ../../third_party/vulkan-validation- > > > layers/src/loader/debug_report.c: In function > > > ‘util_CreateDebugReportCallbacks’: > > > ../../third_party/vulkan-validation- > > > layers/src/loader/debug_report.c:235:5: error: ‘for’ loop initial > > > declarations are only allowed in C99 or C11 mode > > > > Most likely gcc-4.9 defaults to older C standard (C89, I guess). > > The easiest way to solve this would be to update your gcc to 5.4, > > One of these days when I have the time... > > > otherwise you'd have to pass one of the suggested flags to the > > compiler somehow. > > Aren't required gcc versions and/or flags supposed to be specified > in the ebuild?
Compilers are not specified in the ebuild, as the dependency doesn't mean anything - you might have the old still as the selected one. Which you do, which is your problem. Most that could be done is doing a gcc version check early on, as to not wait all this time until the failure before it exits with failure. Everyone is expected to be on at least GCC 5 now. There were some migration things for C++ ABI from GCC 4 to GCC 5 upgrade, but actually that wasn't so much a thing to do on gcc-config switch of compiler, but immediately after GCC 5 install, as libstdc++ symlink isn't controlled by gcc-config afair.
