I emerged Enigma yesterday. It worked fine. Later that day i emerged development-sources 2.6.0 beta 5 and ran emerge -uUD world using ACCEPT_KEYWORDS="~x86". I think a part of SDL was updated. This morning i wanted to start Enigma. The only respond was illegal instruction. Re-emerging crashed. Downgrading libsdl to 1.2.5-r2 had no effect. It won't compile any more. Reproducible: Always Steps to Reproduce: 1. use an up to date gentoo linux using keyword ~x86 2. emerge enigma bash-2.05b$ emerge info Portage 2.0.49-r3 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.6.0-test5) ================================================================= System uname: 2.6.0-test5 i686 Intel(R) Pentium(R) 4 CPU 2.50GHz ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O3 -funroll-loops -pipe -fomit-frame-pointer -ffast-math" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium4 -O3 -funroll-loops -pipe -fomit-frame-pointer -ffast-math" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo http://ftp.easynet.nl/mirror/gentoo/ http://212.219.247.17/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/ebuilds" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts tetex svga java X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome qt kde motif opengl alsa cdr dga directfb dvd faad fbcon ipv6 mozilla pcmcia radeon samba sse tcltk usb wxwindows xinerama xosd xvid -oss gtk gtk2"
Created attachment 17400 [details] Error Log File The error log
what version of lua ? `qpkg -I -v lua`
i used lua 4.0, because the ebuild only allows this one but i modified the ebuild from =dev-lang/lua-4.0" to >=dev-lang/lua-4.0" emerged lua and tried to compile enigma ... no better result, still crashes
I just merged enigma with lua-5.0 so I'm going to update the ebuild. However, since this didn't help you I'm going to assume that you have something else broken on your system. Try this command to see if it works for you: CFLAGS="-pipe" CXXFLAGS="-pipe" emerge media-libs/libsdl media-libs/sdl-mixer media-libs/sdl-image dev-lang/lua games-puzzle/enigma This may be a bit extreme but I suspect one of the packages doesn't like the optimizations you're using. If this command gets you going again with enigma, you can try remerging the five packages again, one at a time, with your current CFLAGS until it breaks. Then, let me know what package broke it all. Thanks.
I tried reemering like you suggested (CFLAGS and CXXFLAGS="-pipe") and still has the same result. I'm going to find out if any other package (any dependency of enigma, and the dependecies of the dependencies) was updated this monday and i will try to reemerge them with simpler CFLAGS and CXXFLAGS.
This might be a gcc 3.3.1 thing. Spanky - can you try merging enigma on your 3.3.1 system and let me know what you come up with please?
You may be right ... i'm updated gcc during the last days, but i'm not sure when exactly :/
i tried another game using sdl (neverball). It compiles, but if i try to start it, it only shows "illegal instruction".
Um...I just noticed this comment in make.conf: # CRITICAL WARNINGS: ****************************************************** # # ATHLON-4 will generate invalid SSE instructions; use 'athlon' instead. # # PENTIUM4 will generate invalid SSE2 instructions; use 'pentium3' instead. # # K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. # # ************************************************************************* # I bet that's your problem. You probably need to rebuild your system without that -march=pentium4 in your CFLAGS.
Refering to: http://forums.gentoo.org/viewtopic.php?t=43373 I don't think so. I also ran the python test line and my system passed this test. So it is something else, i think. But i will give it a try. I will set march=pentium3 and recompile gcc and glibc. But for now i'm downgrading from gcc-3.3.1-r1 to 3.2.3-r2
After downgrading gcc to 3.2.3-r2 and reemerging almost every part of sdl, i was able to compile enigma ... but starting fails and says "Illegal Instruction" Next Test for me: reemerge glibc and after that reemerge sdl
that warning message only applies to gcc-3.2.2 and earlier gcc-3.2.x gcc-3.2.3 fixed the march=p4 bugs (i know cause i had them and then they went away) oddly enough, enigma doesnt even merge on my 3.3.1 box (missing assert.h includes in some files) you dont by chance have multiple versions of gcc emerged do you ? did you set it to gcc-2.x and forget to set it back ?
i only have one version installed (currently 3.3.1-r1). i will try downgrading to 3.2.3-r2 again, this time with VERY soft CFLAGS (something like "-mcpu=pentium4 -pipe") ... but maybe not today
ok, i tried compiling enimga on another machine (athlon-xp, gcc-3.3.1-r1, development-sources-2.6.0-beta5) and it dies at the same point.
aight, the bug is in your system somewhere, and it's not related to enigma ... (1) you said it happened with another program (neverball) (2) enigma works fine on my system with gcc-3.3.1, glibc-2.3.2-r4, 2.6.0-test5 could you give a little background into your system ? like, what versions of glibc/gcc/kernels have you been utilizing ?
bah i just read your error log ... no idea where you saw 'illegal instruction' anywhere so i have no idea what's going on ... i added a patch for the error in your log file, good enough for me
Test System 1: gcc 3.3.1-r1 glibc 2.3.2-r1 kernel 2.6.0-beta5-mm1 Test System 2: gcc 3.3.1-r1 glibc 2.3.2-r1 kernel 2.6.0-beta5 The illegal instruction is when i start the game. The error log only shows what happens when trying to compile.
well re-emerge it and try it again
