On 30/03/18 01:48, P Levine wrote:
> On Wed, Mar 28, 2018 at 8:18 AM, Bill Kenworthy <bi...@iinet.net.au
> <mailto:bi...@iinet.net.au>>wrote:
>
>     I have a compile problem qtgui I cant figure out:
>
>     compilation terminated.
>     make: *** [Makefile:12443: .obj/qaccessible.o] Error 1
>     make: *** [Makefile:12612: .obj/qaccessiblecache.o] Error 1
>     In file included from
>     
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/stl_algo.h:59:0,
>                      from
>     /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/algorithm:62,
>                      from
>     ../../include/QtCore/../../src/corelib/global/qglobal.h:109,
>                      from ../../include/QtCore/qglobal.h:1,
>                      from
>     ../../include/QtGui/../../src/gui/kernel/qtguiglobal.h:43,
>                      from ../../include/QtGui/qtguiglobal.h:1,
>                      from
>     ../../include/QtGui/../../src/gui/image/qimage.h:43,
>                      from ../../include/QtGui/qimage.h:1,
>                      from image/qimage_sse4.cpp:40:
>     /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/cstdlib:75:25:
>     fatal error: stdlib.h: No such file or directory
>      #include_next <stdlib.h>
>
>
>     and of course /usr/include/stdlib.h exists
>
>
>     The actual code in
>     /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/cstdlib is:
>
>     // Need to ensure this finds the C library's <stdlib.h> not a
>     libstdc++
>     // wrapper that might already be installed later in the include
>     search path.
>     #define _GLIBCXX_INCLUDE_NEXT_C_HEADERS
>     #include_next <stdlib.h>
>     #undef _GLIBCXX_INCLUDE_NEXT_C_HEADERS
>
>     Hints welcome!
>
>
>     BillK
>
>
> ​This was a common error from when I ran into when fixing GCC-6
> bugs.​  It's usually related to the fact that GCC-6 doesn't support
> '-isystem /usr/include'.
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129. 
>
>
Thankyou for the references - I will have another go at fixing it
today.  What is confusing me is why its not killing everyones KDE/QT
builds, not just one of mine?


BillK




Reply via email to