Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 39340 - g++ crashed while compiling wxGTK
Summary: g++ crashed while compiling wxGTK
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GCC Porting (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Please assign to toolchain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-25 05:12 UTC by Ricardo Sousa
Modified: 2004-02-01 09:33 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 Ricardo Sousa 2004-01-25 05:12:59 UTC
when compiling wxGTK, it stops in the middle of the compiliation giving the following error:
g++ -c   -I./lib/wx/include/gtk2-2.4 -I./include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES    -D__WXGTK__ -DGTK_NO_CHECK_CASTS -O2 -MMD -O3 -mcpu=i686 -funroll-loops -pipe -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -Wall -fPIC -o listctrl.o ./src/generic/listctrl.cpp
{standard input}: Assembler messages:
{standard input}:8485: Warning: end of file not at end of a line; newline inserted
{standard input}:8708: Error: undefined symbol `.LLSDACSE3180' in operation
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions.
make: *** [listctrl.o] Error 1
make: *** Waiting for unfinished jobs....


Reproducible: Always
Steps to Reproduce:
1.boot
2.emerge wxGTK
3.g++ produces an error




emerge info
Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.4.24)
=================================================================
System uname: 2.4.24 i686 AMD Duron(tm) processor
Gentoo Base System version 1.4.3.10
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://ftp.rnl.ist.utl.pt/gentoo
http://ftp.dei.uc.pt/pub/Linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://ftp.rnl.ist.utl.pt/gentoo-portage"
USE="X aalib apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome
gnome2 gpm gtk gtk2 imlib java jpeg libg++ libwww mad mikmod motif mozilla mpeg
mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime
readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib"
Comment 1 Martin Schlemmer (RETIRED) gentoo-dev 2004-01-26 15:44:05 UTC
That rather sounds like disk space free or a corruption issue.  Sure
you have enough disk space left?   Or maybe a out of memory issue - did
you check dmesg for OOM killer kicking in?

Comment 2 Ricardo Sousa 2004-01-27 17:09:27 UTC
about disk space, here it goes,
df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda2             3.3G  2.3G  1.1G  69% /
none                   63M     0   63M   0% /dev/shm

so this is out of question. :)
i think that's a out of memory issue.
here is dmesg output:
__alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process cc1plus

far from here, it's out from my domain.. 
Comment 3 Ricardo Sousa 2004-01-28 16:18:28 UTC
This is a little weird...
In my other experiences, i was compiling wxGTK under X (witch consumed a lot of memory). Now, i've triyed without X running and it compiled well.

In conclusion, my problems for now are solved, but i will try to reproduce this same situations to debug the error more deeply in hope to fix it.
Comment 4 Martin Schlemmer (RETIRED) gentoo-dev 2004-02-01 09:33:26 UTC
Well, if its OOM, not much I can so.  Unfortunately g++ uses a _log_ of
memory.  You might try to add more swap space?