Bug 191755 - gcc32 cc1 problem
Summary: gcc32 cc1 problem
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc32
Version: 5
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-05-15 16:23 UTC by Luis Uebel
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2006-05-15 16:30:15 UTC

Attachments (Terms of Use)

Description Luis Uebel 2006-05-15 16:23:00 UTC
Description of problem:
I tried to compile Flite (a small version of Festival) -
Sunday morning, I changes calls (./config/config) for gcc (gcc 4.1 in
my system) to gcc32 and worked. Programs compiled fine. Sunday afternoon
I update system for last kernel version 2111 and program stopped to 

gcc32   -I../../lang/usenglish  -I../../lang/cmulex -I../../include -g -O2 -Wall
   -c cmu_us_kal16_res.c -o
gcc32: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make[2]: ***
[../../build/i386-linux-gnu/obj/lang/cmu_us_kal16/cmu_us_kal16_res.o] Error 1
make[1]: *** [../build/i386-linux-gnu/obj/lang/.make_build_dirs] Error 2
make: *** [build/i386-linux-gnu/obj//.make_build_dirs] Error 2

I don't remember all packages that I update, but were related with kernel,
selinux, nmap, xemacs, etc.

Version-Release number of selected component (if applicable):
 Flite version 1.3

How reproducible:

Please, see description above.

Steps to Reproduce:
1. download program.
2. unpack
3. change ./config/config (gcc for gcc32).
4. Compile.

Actual results:

Expected results:

Additional info:
I am using a Toshiba Satellite, 512 Mbytes, 512 Mbyte of swap, FC5.

Comment 1 Jakub Jelinek 2006-05-15 16:30:15 UTC
This means gcc got killed by OOM killer, 512MB RAM/swap really isn't much
for many larger sources especially when you have other apps running.
Try increasing the size of your swap or decrease the number of other apps running
at the same time.

gcc32 is provided as is just for compatibility, so even if GCC 3.2.x was too much
memory hungry on the source, it will stay that way.

Note You need to log in before you can comment on or make changes to this bug.