Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 9411 - kdelibs compile failure in vicinity of kio
Summary: kdelibs compile failure in vicinity of kio
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-20 19:45 UTC by Whit Blauvelt
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Whit Blauvelt 2002-10-20 19:45:07 UTC
Not sure what was before this, but the screen at time of failure read:

la.all_cpp.cpp  -fPIC -DPIC -o .libs/libksycoca_la.all_cpp.o
/usr/sbin/sendmail: can't open the smtp port (25) on mail.
i686-pc-linux-gnu-g++: Internal error: Terminated (program cc1plus)
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[3]: *** [libksycoca_la.all_cpp.lo] Error 1
{standard input}: Assembler messages:
{standard input}:119273: Warning: end of file not at end of a line; newline
inserted
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory
`/var/tmp/portage/kdelibs-3.0.4/work/kdelibs-3.0.4/kio/kio'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kdelibs-3.0.4/work/kdelibs-3.0.4/kio'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kdelibs-3.0.4/work/kdelibs-3.0.4'
make: *** [all] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function kde_src_compile, Line -6658, Exitcode 2
!!! died running emake, kde_src_compile:make
la.all_cpp.cpp  -fPIC -DPIC -o .libs/libksycoca_la.all_cpp.o
/usr/sbin/sendmail: can't open the smtp port (25) on mail.
i686-pc-linux-gnu-g++: Internal error: Terminated (program cc1plus)
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[3]: *** [libksycoca_la.all_cpp.lo] Error 1
{standard input}: Assembler messages:
{standard input}:119273: Warning: end of file not at end of a line; newline
inserted
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory
`/var/tmp/portage/kdelibs-3.0.4/work/kdelibs-3.0.4/kio/kio'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/kdelibs-3.0.4/work/kdelibs-3.0.4/kio'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/kdelibs-3.0.4/work/kdelibs-3.0.4'
make: *** [all] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function kde_src_compile, Line -6658, Exitcode 2
!!! died running emake, kde_src_compile:make
Comment 1 Dan Armak (RETIRED) gentoo-dev 2002-10-21 10:16:44 UTC
I don't think the sendmail message is related to the compile error (at least I hope  
not! :-).  
 
An internal compiler error is likely enough generated because of an incomplete gcc 
ugprade. Did you ever upgrade gcc on this system? 
  
Comment 2 Whit Blauvelt 2002-10-21 11:02:30 UTC
(Of course I didn't think the sendmail message meant anything; was just doing a
cut-and-paste of the screen at the time of failure;)

The gcc on the system is that included in stage3-i686-1.4_rc1.tar.bz2 (gcc -v
output at end here). It has not been upgraded past that point. Should I
reinstall (rebuild?) gcc? 

Or - as was suggested in reaction to my earlier reporting of a bug (which seemed
to be related to attempting to build kde from within a chroot rather than an
actual Gentoo boot) - would the suspected culprit be that this Pentium Pro is
running but 64 megs of ram with a 128 meg swap file, causing gcc to simply
exhaust memory and fail? I have more memory on order, so can test that
conjecture within a week. If it is too little memory, it would be nice to see
the actual requirement stated upfront in the Gentoo docs, which currently cite
what I have as minimally sufficient - but perhaps that only means for a
nongraphical Gentoo?

gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
Configured with: /var/tmp/portage/gcc-3.2-r1/work/gcc-3.2/configure
--prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared
--host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i686-pc-linux-gnu
--with-system-zlib --enable-languages=c,c++,ada,f77,objc,java
--enable-threads=posix --enable-long-long --disable-checking
--enable-cstdio=stdio --enable-clocale=generic --enable-__cxa_atexit
--enable-version-specific-runtime-libs
--with-gxx-include-dir=/usr/include/g++-v32 --with-local-prefix=/usr/local
--enable-shared --enable-nls --without-included-gettext
Thread model: posix
gcc version 3.2
Comment 3 Hannes Mehnert (RETIRED) gentoo-dev 2002-10-21 11:29:23 UTC
please remove --enable-final from kdelibs ebuild and compile kdelibs again.  
--enable-final needs lot of memory/swap. 
Comment 4 Whit Blauvelt 2002-10-22 00:15:57 UTC
Removing --enable-final from the kdelibs ebuild resulted in a successful compile
(in 13+ hours ;) of kdelibs. Would a useful enhancement be an amount-of-memory
conditional that would determine whether memory-intensive flags like
--enable-final were enabled for a package? There'd still be a fuzziness because
of other processes running on the system being indeterminate, but a rule like
"if less than 256 megs, don't --enable-final" could be usefully automated.
Meanwhile whatever the effective limit is could be mentioned in the Desktop doc.
Comment 5 Dan Armak (RETIRED) gentoo-dev 2002-10-29 15:10:15 UTC
I've nw put such an automated check in kde-functions.eclass; it turns --enable-final 
off if less than 200MB of ram+swap is available (free). Seems like a safe enough 
limit. 
Comment 6 Whit Blauvelt 2002-10-29 15:44:17 UTC
This would probably also be the solution to Bug 9482 (there involving the
kde-dist.eclass)?