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