var/tmp/portage/basiliskII-1.0.0/temp/ccQxJTmG.s:11415: Warning: translating to `fmulp' var/tmp/portage/basiliskII-1.0.0/temp/ccQxJTmG.s:11368: Warning: translating to `faddp' var/tmp/portage/basiliskII-1.0.0/temp/ccQxJTmG.s:1857: Warning: translating to `fmulp' var/tmp/portage/basiliskII-1.0.0/temp/ccQxJTmG.s:1848: Warning: translating to `fmulp' var/tmp/portage/basiliskII-1.0.0/temp/ccQxJTmG.s:1839: Warning: translating to `fmulp'
var/tmp/portage/basiliskII-1.0.0/temp/ccQxJTmG.s:1830: Warning: translating to `fmulp' var/tmp/portage/basiliskII-1.0.0/temp/ccQxJTmG.s: Assembler messages: I./uae_cpu -DHAVE_CONFIG_H -DOS_linux -DCPU_i386 -DDIRECT_ADDRESSING -fno-strength-reduce -DSAHF_SETO_PROFITABLE -DUNALIGNED_PROFITABLE -DREGPARAM="_attribute_((regparm(3)))" -DX86_ASSEMBLY -DOPTIMIZED_FLAGS -DFPU_X86 -D_REENTRANT -DDATADIR=\"/usr/share/BasiliskII\" -march=pentium4 -mcpu=pentium4 -O2 -fforce-addr -foptimize-sibling-calls -fmerge-all-constants -fprefetch-loop-arrays -finline-functions -ffast-math -funroll-loops -mno-3dnow -maccumulate-outgoing-args -msse -msse2 -mmmx -mfpmath=sse -I/usr/X11R6/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -I/usr/include/gnome-1.0 -DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -fno-exceptions -fno-merge-constants -c. Here's what the current Basilisk II ebuild gives me, btw: The homepage points to the JIT version's homepage too, which is probably wrong too: The JIT version has been merged with the original.īlargh, just gonna shamelessly bump this. It's a cvs snapshot of the JIT version from a couple of months ago (fails to compile here too). The official hompage of Basilisk II is here:ītw: the Basilisk II ebuild found in portage is just. Right now I don't think it's worth diving into that crash, because obviously autotools isn't really helping out here and there might actually be more problems with the configure script than I've shown here. I don't see what's wrong with it except that maybe _USE_BSD shouldn't be defined? Surely this header is used by a thousand more apps out there and they all compiled flawlessly.Īfter the compile, launching Basilisk II seems to work at first sight, but when trying to start the emulation it flashes an empty white window prior to crashing. This is what the sys/types.h section looks like that's causing problems: Commenting out those two lines in sys/types.h (and defining STDC_HEADERS) seems to fix this and compile. But it's not something within basilisk's power. I have no idea what check that exactly is in configure.ac. usr/include/sys/types.h:117: syntax error before ` ' tokenĬonfig.h doesn't have STDC_HEADERS defined somehow. Sysdeps.h:32:2: #error "You don't have ANSI C header files."
I./uae_cpu -DHAVE_CONFIG_H -DOS_linux -DDIRECT_ADDRESSING -DUSE_JIT -DUSE_JIT_FPU -DFPU_IEEE -D_REENTRANT -DDATADIR=\"/usr/local/share/BasiliskII\" -g -O2 -I/usr/X11R6/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -I/usr/include/gnome-1.0 -DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -c. Moving on, when trying to compile I get the following errors at the very first file: I've taken a look at /usr/share/aclocal and AC_EGREP_CPP seems to be not widely used. The _GNUC_ and _GNUC_MINOR_ definitly exist and are correct, so it's not something in my compiler. Obviously it's the AC_EGREP_CPP failing here. I haven't checked the complete configure output yet but there's some things in there that definitly stand out as incorrect. Trying to compile a BasiliskII snapshot alot of things seem to go wrong. Posted: Mon 12:38 pm Post subject: Autotools difficulties with Basilisk II CVS Gentoo Forums Forum Index Portage & Programming Gentoo Forums :: View topic - Autotools difficulties with Basilisk II CVSĪutotools difficulties with Basilisk II CVS
0 kommentar(er)
