Bug 77743 – emerge qt failed

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description David Mulford 2005-01-12 14:27:35 UTC]

When trying to emerge gaim, one of the dependencies is qt-3.3.3 which will not compile.  Here are the errors I am getting:

g++: Internal error: Terminated (program cc1plus)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions.
make[3]: *** [formwindow.o] Error 1
{standard input}: Assembler messages:
{standard input}:14376: Warning: end of file not at end of a line; newline inser                  ted
{standard input}:14505: Error: no such instruction: `su'
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/too                  ls/designer/designer'
make[2]: *** [sub-designer] Error 2
make[2]: Leaving directory `/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/toos/designer'
make[1]: *** [sub-designer] Error 2
make[1]: Leaving directory `/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/tools'
make: *** [sub-tools] Error 2

!!! ERROR: x11-libs/qt-3.3.3 failed.
!!! Function src_compile, Line 126, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.

This always happens just after trying to compile windowform.cpp
I've searched all the bugs for qt. None of which have the exact same error and none of which the proposed solutions work.

Thanks in advance,
David

Reproducible: Always
Steps to Reproduce:
1. emerge gaim
2.
3.

Actual Results:  
Compile errors, as seen above.

Expected Results:  
emerge qt nicely then continue emerging gaim.

I read in another bug that it could be stressing the system, such as CPU getting
too hot or bad memory.

I know the memory is good.

I'm installing on a laptop, so I propped the laptop up and put a fan blowing
directly on it. I am running gkrellm and watched the temperature drop about 40
degrees, so if that was the problem before, it's not now.

;)

[Comment 1 Gregorio Guidi (RETIRED) 2005-01-12 16:30:05 UTC]

You forgot your 'emerge info'

the failure you're seeing is on one of the most complex (and cpu intensive) 
files... also, it needs a lot of ram to compile, maybe you're going out of ram
at that point?

[Comment 2 David Mulford 2005-01-13 09:17:12 UTC]

it's most likely the computer going out of ram, as I only have 128MB in this laptop and am currently looking to buy more. How would I check if it is indeed using all the ram during the compilation process? 

also, is there a work around for this sort of problem?

[Comment 3 Gregorio Guidi (RETIRED) 2005-01-13 09:50:34 UTC]

That's likely to be the cause.

you can try setting up a swap partition if you didn't already, and not using "-pipe" in cflags (and using low optimizations might help, too)

To monitor your ram, you can try to look at the output of 'free', but that
just gives a rough idea, I don't know a more precise method.

[Comment 4 David Mulford 2005-01-14 16:26:29 UTC]

Setting "-pipe" in CFLAGS worked for me. I did not change the optimizations.  I was definitely using all the RAM in the system, and not using -pipe worked.

Thanks!

PS: I'm not sure what to status this bug as now. So, if anyone could point me in the right direction, or just status it, that would be great.