[gentoo-user] cant find stdlib.h

[Bill Kenworthy]

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

[Pengcheng Xu]

I had ran into this before (but on Gentoo FreeBSD); maybe the compile command line

had stray -isystem in it, thus disturbing the include search path.

Pengcheng Xu

i...@jsteward.moe

H30/03/28 20:18、Bill Kenworthy <bi...@iinet.net.au>のメール:

[P Levine]

​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. 

[Bill Kenworthy]

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:

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

[Bill Kenworthy]

and I should have asked, is there an easy way to fix it? ... and should
I raise a bug or is it a one off on just this system?


BillK

[P Levine]

​Idk.  Those bugs were fixed a while ago.  Are you sure you're you're using an updated ebuild from the main Gentoo​ repo?  If you're using stable keyworded QT, try keyword unmasking unstable qt packages and see if that helps.  If so, you might want to file a bug.

and I should have asked, is there an easy way to fix it?

​It depends.  Usually it requires editing qmake .pro file(s).

[Bill Kenworthy]

On 30/03/18 10:25, P Levine wrote:
>
>
> On Thu, Mar 29, 2018 at 6:42 PM, Bill Kenworthy <bi...@iinet.net.au
> <mailto:bi...@iinet.net.au>> wrote:
>
> 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>

> > <mailto:bi...@iinet.net.au <mailto:bi...@iinet.net.au>>>wrote:

> <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
>
>
> ​Idk.  Those bugs were fixed a while ago.  Are you sure you're you're
> using an updated ebuild from the main Gentoo​ repo?  If you're using
> stable keyworded QT, try keyword unmasking unstable qt packages and
> see if that helps.  If so, you might want to file a bug.
>
> and I should have asked, is there an easy way to fix it?
>
>
> ​It depends.  Usually it requires editing qmake .pro file(s).

I found the bug against gcc for it (not qtgui which is why I couldnt
find any info on the problem). Seems that its one of the source packages
polutes the build environment at some point in the past so I have to go
back and fix those first.


BillK

'