Summary: | KDELIBS Fails to Build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sean P. Kane <spkane> |
Component: | [OLD] KDE | Assignee: | Dan Armak (RETIRED) <danarmak> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | spkane |
Priority: | High | ||
Version: | 1.1a | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sean P. Kane
2002-04-20 14:12:05 UTC
This isn't a freeze. Just a long compile :-) We use the --enable-all configure parameter when compiling kdelibs. This dumps lots of cpp files into one bug fie and compiles it instaed. It results in better compile time overall, but instead of seeing for 30 minutes individual files being compiles, you just see one big file for 20 minutes, which can look like a freeze, but isn't. Disregard the #warning, it's always printed and is harmless. So: try waiting. For a p3-900 with 256MB ram (what I have), wait at least 15 minutes. Memory is crucial, so if you have only half as much, you'll have to wait twice as long. Try leaving it in the background for an hour and see if it makes any progress to be sure. If the --enable-all option really annoys you, you can edit /usr/portage/eclass/kde-base.eclass and delete the line that says myconf="$myconf --enable-all" ...but it'll get back whenever you emerge rsync. Can't do anything about that. Hi, It's been brought up recently that with the default bugzilla user config, the submitter of a bug isn't mailed automatically when comments are added to that bug. So you may not have recieved my instructions. In that case please look at them now. Or tell me if the problem is no longer relevant. I had to rebuild my system an ran into a bunch of problems, and have not been able to retest this. I have my system back up so I will check this in the next few days. Thanks, Sean I have since set my system to "use -kde" so this is no longer an immediate problem. If it shows up again and the suggested fix doesn't work, I'll let you know. Thanks, Sean Sorry, but it's NOT just a long compile... -> 2. time it comes with: "...In file included from libkdecore_la.all_cpp.cpp:23: kcharsets.cpp:420: warning: #warning FIXME?" It writes: cpp0:g++: output pipe has been closed Internal compiler error: program cc1plus got fatal signal 15 {standard input}: Assembler messages: {standard input}:285453: Warning: end of file not at end of a line; newline inserted make[3]: *** [libkdecore_la.all_cpp.lo] Error 1 make[3]: Leaving directory '/var/tmp/portage/kdelibs-3.0-r1/work/kdelibs-3.0/kdecore' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/var/tmp/portage/kdelibs-3.0-r1/work/kdelibs-3.0/kdecore' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/var/tmp/portage/kdelibs-3.0-r1/work/kdelibs-3.0' make: *** [all] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Funktion kde_src_compile, Line -3694, Exitcode 2 !!! died running emake, kde_src_compile:make !!! emerge aborting on /var/tmp/portage/kdelibs-3.0-r1.ebuild . localhost root # Claus |