Guys,
This craziness with gcc may actually be a compiler error. Here is the latest error I got with kdebase:
[18%] Building CXX object kcontrol/konq/CMakeFiles/kcm_konq-module.dir/fontopts.cpp.o cd /home/david/tbld/kdebase/src/kcontrol/konq && /usr/bin/c++ -Dkcm_konq_module_EXPORTS -DHAVE_CONFIG_H -DUSE_QT3 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -march=i686 -mtune=generic -O2 -pipe -include tqt.h -fPIC -I/home/david/tbld/kdebase/src/kcontrol/konq -I/home/david/tbld/kdebase/src -I/home/david/tbld/kdebase/libkonq -I/opt/trinity/include -I/opt/qt/include -I/opt/qt/include/tqt -o CMakeFiles/kcm_konq-module.dir/fontopts.cpp.o -c /home/david/tbld/kdebase/kcontrol/konq/fontopts.cpp In file included from /home/david/tbld/kdebase/kcontrol/konq/fontopts.cpp:387:0: /home/david/tbld/kdebase/src/kcontrol/konq/fontopts.moc: In member function ■virtual void KonqFontOptions::load(bool)■: /home/david/tbld/kdebase/src/kcontrol/konq/fontopts.moc:136:93: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. make[2]: *** [kcontrol/konq/CMakeFiles/kcm_konq-module.dir/fontopts.cpp.o] Error 1 make[2]: Leaving directory `/home/david/tbld/kdebase/src' make[1]: *** [kcontrol/konq/CMakeFiles/kcm_konq-module.dir/all] Error 2 make[1]: Leaving directory `/home/david/tbld/kdebase/src' make: *** [all] Error 2 Aborting...
On 02/11/2011 12:25 PM, David C. Rankin wrote:
Guys,
This craziness with gcc may actually be a compiler error. Here is the latesterror I got with kdebase:
[18%] Building CXX object kcontrol/konq/CMakeFiles/kcm_konq-module.dir/fontopts.cpp.o cd /home/david/tbld/kdebase/src/kcontrol/konq && /usr/bin/c++ -Dkcm_konq_module_EXPORTS -DHAVE_CONFIG_H -DUSE_QT3 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -march=i686 -mtune=generic -O2 -pipe -include tqt.h -fPIC -I/home/david/tbld/kdebase/src/kcontrol/konq -I/home/david/tbld/kdebase/src -I/home/david/tbld/kdebase/libkonq -I/opt/trinity/include -I/opt/qt/include -I/opt/qt/include/tqt -o CMakeFiles/kcm_konq-module.dir/fontopts.cpp.o -c /home/david/tbld/kdebase/kcontrol/konq/fontopts.cpp In file included from /home/david/tbld/kdebase/kcontrol/konq/fontopts.cpp:387:0: /home/david/tbld/kdebase/src/kcontrol/konq/fontopts.moc: In member function ■virtual void KonqFontOptions::load(bool)■: /home/david/tbld/kdebase/src/kcontrol/konq/fontopts.moc:136:93: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. make[2]: *** [kcontrol/konq/CMakeFiles/kcm_konq-module.dir/fontopts.cpp.o] Error 1 make[2]: Leaving directory `/home/david/tbld/kdebase/src' make[1]: *** [kcontrol/konq/CMakeFiles/kcm_konq-module.dir/all] Error 2 make[1]: Leaving directory `/home/david/tbld/kdebase/src' make: *** [all] Error 2 Aborting...
This looks like it was just a transient bit flip somewhere in the virtualbox environment. Building as second time produced no such error at 18%. So we are still stuck at the iccconfig.cpp KRandrSimpleAPI build crash on kdebase. I have put the full output of the kdebase (tee'd into the following file) here:
http://www.3111skyline.com/dl/dt/trinity/errors/kdebase-scroll.txt
I have also tarred and bzipped the kdebase/src/kcontrol/iccconfig dir here showing the exact state of it during the build failure:
http://www.3111skyline.com/dl/dt/trinity/errors/kcontrol_iccconfig-src.tar.b...
Let me know if you have any ideas. Thanks.
On 02/11/2011 12:25 PM, David C. Rankin wrote:
Guys,
This craziness with gcc may actually be a compiler error. Here is the latesterror I got with kdebase:
<snip>
For those interested:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47723
On 02/11/2011 12:25 PM, David C. Rankin wrote:
Guys,
This craziness with gcc may actually be a compiler error. Here isthe latest error I got with kdebase:
<snip>
For those interested:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47723
--
That would definitely be a possible explanation for the problem, and why you currently seem to be the only one running into it. GCC bugs are rare, but they take a long time to identify as an actual compiler problem and not just a code/build environment problem.
Can you try with an older version of GCC (e.g. 4.3 or 4.4) and see if you still encounter the problem?
Thanks!
Tim
On 02/13/2011 05:03 PM, Timothy Pearson wrote:
That would definitely be a possible explanation for the problem, and why you currently seem to be the only one running into it. GCC bugs are rare, but they take a long time to identify as an actual compiler problem and not just a code/build environment problem.
Can you try with an older version of GCC (e.g. 4.3 or 4.4) and see if you still encounter the problem?
Thanks!
Tim
Yes, thanks Tim,
I'll look through my old packages and see if I still have an earlier GCC. If not, I'll figure out how to rebuild one and how much stuff I'll break doing it :)
-
David C. Rankin -
Timothy Pearson