Bug 392461 - gcc error while compling IRCD
Summary: gcc error while compling IRCD
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: i386
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-20 14:42 UTC by Jason
Modified: 2007-12-06 13:14 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-12-06 13:14:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jason 2007-11-20 14:42:43 UTC
Description of problem:

While compiling IRCD in an vps I facing the error.


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


How reproducible:
#/home/root/ircd/unreal
#./Config
#make

 

Error Message:

gcc -I../include -I/home/ftpuser/ircd/extras/regexp/include
-I/home/ftpuser/ircd/extras/c-ares/include -L../extras/c-ares/lib -pipe -g -O2
-funsigned-char -fno-strict-aliasing -export-dynamic   -c s_conf.c
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make[1]: *** [s_conf.o] Error 1
make[1]: Leaving directory `/home/ftpuser/ircd/src'
make: *** [build] Error 2
[root@www ircd]# {standard input}: Assembler messages:
{standard input}:11522: Warning: end of file not at end of a line; newline inserted
{standard input}:12729: Error: unknown pseudo-op: `.'

Comment 1 David Lawrence 2007-11-20 15:04:59 UTC
Changing to proper product/component so a developer will see this bug.

Comment 2 Jakub Jelinek 2007-11-23 16:46:50 UTC
This is kernel OOM killer which killed gcc, so unless gcc was using unreasonably
too much memory on a simple testcase, it is not a gcc bug.
If you can reproduce it always with the same source, please attach it
preprocessed.

Comment 3 Jason 2007-11-24 10:41:18 UTC
This issue was fixed just by restarting that vps server. It was consuming more
memory and process limit.

Thanks for your effort and time. 


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