During an "emerge -uNDav @world" lxqt-base/lxqt-config-0.9.0 should have been emerged but instead the compile broke apparently dur to errors in the source code. I've attached the build log and the emerge info
Created attachment 412404 [details] Build log
Created attachment 412408 [details] Emerge info
Please, submit build logs for compilation with '-j1' option. This makes reading them a way easier.
Please, try to compile with the stable GCC (4.8.*) and show the results.
Created attachment 413156 [details] New build log with gcc-4.8 and -j1 I downgraded to gcc-4.8, as requested, and re-emerged. I still get the same error. I ran `emerge -j1 -1 lxqt-config`
Created attachment 413158 [details] New emerge info An updated emerge info
Created attachment 413160 [details] Output of emerge -pqv '=lxqt-base/lxqt-config-0.9.0::gentoo' Just in case
(In reply to James Dominy from comment #5) > Created attachment 413156 [details] > New build log with gcc-4.8 and -j1 > > I downgraded to gcc-4.8, as requested, and re-emerged. I still get the same > error. I ran `emerge -j1 -1 lxqt-config` Citation from your build log: > make -j5 VERBOSE=1 Please, read some documentation and add '-j1' option to your make.conf file. Namely, add MAKEOPTS="-j1" to /etc/portage/make.conf. Then, rebuild, please and post here the log.
(In reply to James Dominy from comment #5) > Created attachment 413156 [details] > New build log with gcc-4.8 and -j1 > > I downgraded to gcc-4.8, as requested, and re-emerged. I still get the same > error. I ran `emerge -j1 -1 lxqt-config` Another citation from yopur build log: > -- The C compiler identification is GNU 4.9.3 > -- The CXX compiler identification is GNU 4.9.3 Please, consider reading some documentation about switching gcc in Gentoo. Use gcc-config for switching.
Created attachment 414414 [details] New build log with gcc-4.8 and -j1 (having actually switched gcc) Sorry, I forgot to actually switch gcc profiles. Done now, here's the output of `gcc-config -l` $ gcc-config -l [1] x86_64-pc-linux-gnu-4.8.5 * [2] x86_64-pc-linux-gnu-4.9.3 Also, here's the updated build log
Created attachment 414416 [details] New emerge info And here's the updated emerge info
Thank you for update. Sorry for long reply, I'll look at this issue in the nearest time (should be this weekend).
Ok, I've looked at your logs for gcc-4.8, build failed because of other problems: failure probably is caused by switch to the old version of gcc without rebuilding libraries, but gcc-4.9.3 is stable now and I have it on my machine, so I'm going to investigate the original issue. For now I suggest you switching back to gcc-4.9.3 also I suggest you not to use unstable versions of the base system packages (like gcc) until you really understand what you are doing -- you'll have less failures. You'd better use the latest stable version of libc, gcc and other similar stuff until you have really good reasons to use something unstable.
I can't reproduce the original error for gcc-4.9.3. Could you, please, try to reproduce it once again with this version of compiler and post here the log for -j1.
Created attachment 415090 [details] info.txt confirmed here at the tindebox with -j1 ----------------------------------------------------------------- This is an unstable amd64 chroot image (named amd64-desktop-unstable_20151004-161203) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- Portage 2.2.23 (python 3.4.3-final-0, default/linux/amd64/13.0/desktop, gcc-4.8.5, glibc-2.22-r1, 4.2.3-hardened-r4 x86_64)
Created attachment 415094 [details] emerge-history.txt
Created attachment 415096 [details] environment
Created attachment 415098 [details] lxqt-base:lxqt-config-0.9.0:20151021-001618.log
Created attachment 415238 [details, diff] Fix This patch fix it for me
I can confirm the patch from #19 fixes the issue. thanks Yuriy!
I can confirm too that the patch from #19 fixes the issue. https://github.com/Sabayon/for-gentoo/commit/686bf376bc85573b0e262f3279bb16b2055a5cf2 tested it on arm
It's fixed upstream in 0.10
