Re: [gentoo-user] cant find stdlib.h

[P Levine]

On Thu, Mar 29, 2018 at 6:42 PM, Bill Kenworthy  wrote:

> On 30/03/18 01:48, P Levine wrote:
> > On Wed, Mar 28, 2018 at 8:18 AM, Bill Kenworthy  > >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 
> >
> >
> > 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  not a
> > libstdc++
> > // wrapper that might already be installed later in the include
> > search path.
> > #define _GLIBCXX_INCLUDE_NEXT_C_HEADERS
> > #include_next 
> > #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
>

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

Re: [gentoo-user] cant find stdlib.h

[Bill Kenworthy]

On 30/03/18 06:42, Bill Kenworthy wrote:
> On 30/03/18 01:48, P Levine wrote:
>> On Wed, Mar 28, 2018 at 8:18 AM, Bill Kenworthy > >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 
>>
>>
>> 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  not a
>> libstdc++
>> // wrapper that might already be installed later in the include
>> search path.
>> #define _GLIBCXX_INCLUDE_NEXT_C_HEADERS
>> #include_next 
>> #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
>
>
>
>
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

Re: [gentoo-user] cant find stdlib.h

[Bill Kenworthy]

On 30/03/18 01:48, P Levine wrote:
> On Wed, Mar 28, 2018 at 8:18 AM, Bill Kenworthy  >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 
>
>
> 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  not a
> libstdc++
> // wrapper that might already be installed later in the include
> search path.
> #define _GLIBCXX_INCLUDE_NEXT_C_HEADERS
> #include_next 
> #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

Re: [gentoo-user] cant find stdlib.h

[P Levine]

On Wed, Mar 28, 2018 at 8:18 AM, Bill Kenworthy  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 
>
>
> 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  not a libstdc++
> // wrapper that might already be installed later in the include search
> path.
> #define _GLIBCXX_INCLUDE_NEXT_C_HEADERS
> #include_next 
> #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.

Re: [gentoo-user] sys-libs/e2fsprogs-libs causing sandbox violation in /root/.ccache?

[Jack]

On 2018.03.29 00:33, P Levine wrote:

Th
​is has been going on for the last few months.  It only seems to  
happen for
sys-libs/e2fsprogs-libs.  I haven't filed a bug yet as I'm unsure if  
there
is something I'm overlooking on my end.  I can delete /root/.ccache  
and
remerge and it seems to be fine after that, but while updating the  
world a

few weeks later it sporadically returns.

The relevant part of the build:

make[1]: 'compile_et' is up to date.
> make[1]: Leaving directory
>  
'/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-ab

> i_x86_64.amd64/lib/et'
> making all in lib/et
> * ACCESS DENIED:  utimes:   /root/.ccache
> * ACCESS DENIED:  mkdir:/root/.ccache/3
> make[1]: Entering directory
>  
'/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-a

> bi_x86_64.amd64/lib/et'
> make[1]: Nothing to be done for 'all'.
> make[1]: Leaving directory
>  
'/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-ab

> i_x86_64.amd64/lib/et'


​And the sandbox report:​

* --- ACCESS VIOLATION SUMMARY
> ---
> * LOG FILE: "/var/log/sandbox/sandbox-28430.log"
> *
> VERSION 1.0
> FORMAT: F - Function called
> FORMAT: S - Access Status
> FORMAT: P - Path as passed to function
> FORMAT: A - Absolute Path (not canonical)
> FORMAT: R - Canonical Path
> FORMAT: C - Command Line
>
> F: utimes
> S: deny
> P: /root/.ccache
> A: /root/.ccache
> R: /root/.ccache
> C: x86_64-pc-linux-gnu-gcc -x c -v -c /dev/null -o /dev/null
> F: mkdir
> S: deny
> P: /root/.ccache/3
> A: /root/.ccache/3
> R: /root/.ccache/3
> C: x86_64-pc-linux-gnu-gcc -x c -v -c /dev/null -o /dev/null
> *
>  




Has anyone else run into sporadic build failures like this?

I've had similar issues with various ebuilds, for me most commonly  
nodejs.  It's because of some XDG... environment variable.  Before you  
do the emerge, either do "su -"
 or something else to clear the environment.  It's not really anything  
specific to the ebuild, other than emerge not sanitizing the  
environment first.


Also, what I have sometimes done as a temporary workaround to save  
redoing the compile is to manually go to the build directory and type  
"make" to complete the compile, then complete the remaining ebuild  
steps (install and qmerge, I think - from memory).


Jack

Re: [gentoo-user] [SOLVED] gcc-6.4.0-r1::gentoo failed (compile phase)

[J García]

2018-03-28 12:08 GMT-06:00  :

> I'm still searching for a good guid howto over NFS.
> It is till not clear to me what to do before or after.  I need to start
> with emerging NFS :-/
>
> On my Atom-330 with MAKEOPTS="-j1" it took me over 12-hours to compile
> just gcc-6.4.0-r1 :-/
> and I have server on that network 8-core AMD with 32-GB or RAM (so I
> might as well put it into a good use).
I would not bother with NFS for this, portage has some options you can
add to make.conf to transfer the binary packages using HTTP, namely
FEATURES=getbinpkg and the variable PORTAGE_BINHOST, you can add those
to the less powerful machine, check the manual about make.conf for the
details on each.
An example:
PORTAGE_BINHOST="http://10.0.0.X:8000;
Just make it appropriate for your LAN, then run a simple HTTP server
on the directory that contains the binary packages on the powerful
machine, no need install any HTTP server package, python can do it
[1][2]:
For example:
$ cd $PKGDIR
$ python2 -m SimpleHTTPServer 8000
or
$ python3 -m http.server 8000
You can even add that as part of the service that creates the chroot
as suggested before.
.
[1] 
https://docs.python.org/3.6/library/http.server.html?highlight=httpserver#module-http.server
[2] 
https://docs.python.org/2/library/simplehttpserver.html#module-SimpleHTTPServer

Re: [gentoo-user] sys-libs/e2fsprogs-libs causing sandbox violation in /root/.ccache?

[Rich Freeman]

On Thu, Mar 29, 2018 at 8:46 AM, J García  wrote:
> 2018-03-28 22:33 GMT-06:00 P Levine :
>
>> The relevant part of the build:
>>
>>> make[1]: 'compile_et' is up to date.
>>> make[1]: Leaving directory
>>> '/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-ab
>>> i_x86_64.amd64/lib/et'
>>> making all in lib/et
>>> * ACCESS DENIED:  utimes:   /root/.ccache
>>> * ACCESS DENIED:  mkdir:/root/.ccache/3
>
> The ebuild is working fine on my end, it was built yesterday with no
> issues according to my logs. Is FEATURES=ccache part of your
> make.conf?
> If it is, try to build it with without that feature.

That would almost certainly make the problem go away.

I don't have this issue with e2fsprogs-libs-1.43.6 with ccache, so the
issue is either specific to the newer version or something wrong with
the local config.

-- 
Rich

Re: [gentoo-user] sys-libs/e2fsprogs-libs causing sandbox violation in /root/.ccache?

[J García]

2018-03-28 22:33 GMT-06:00 P Levine :

> The relevant part of the build:
>
>> make[1]: 'compile_et' is up to date.
>> make[1]: Leaving directory
>> '/var/tmp/portage/sys-libs/e2fsprogs-libs-1.44.1/work/e2fsprogs-libs-1.44.1-ab
>> i_x86_64.amd64/lib/et'
>> making all in lib/et
>> * ACCESS DENIED:  utimes:   /root/.ccache
>> * ACCESS DENIED:  mkdir:/root/.ccache/3

The ebuild is working fine on my end, it was built yesterday with no
issues according to my logs. Is FEATURES=ccache part of your
make.conf?
If it is, try to build it with without that feature.


PD: HTML is not welcome in the messages for this list, not everyone is
reading this list with an HTML capable mail reader, those people are
only able to see a bunch of garbage if you send it this way.
Many will ignore your message because of that. Next time just send plain text.