RE: [B2-devel] Can't run BasiliskII on Fedora Core 3 x86

[Tomek J. <to...@je...>]

 
> Matthias Saou wrote :
> 
> > This is my first attempt at running BasiliskII, and I've tried just 
> > about all and any sources, binaries that I could find, with 
> many many 
> > different settings combinations and both Mac IIci and Quadra 900 
> > BIOSes without
> being
> > able to get it to work properly. [...]
> 
> Silence... so I'll reply to myself ;-)
> Since the error I reported seemed optimisation related, I 
> tried both forcing the disabling of X86 assembly usage, and 
> recompiling on my Fedora Core 3 x86_64 system, but I get the 
> same asm error in both cases. Seems like the current CVS is 
> quite x86-centric, or maybe those are just problems with gcc 3.4 :
> 
> g++ -I../include -I. -I../uae_cpu -DHAVE_CONFIG_H  -DOS_linux
> -DDIRECT_ADDRESSING -DUNALIGNED_PROFITABLE -DX86_64_ASSEMBLY 
> -DOPTIMIZED_FLAGS -DUSE_JIT -DUSE_JIT_FPU -DFPU_IEEE 
> -D_REENTRANT -DDATADIR=\"/etc/BasiliskII\" -O2  -pipe -m64 
> -I/usr/include/SDL -D_REENTRANT -I/usr/include/gtk-1.2 
> -I/usr/include/glib-1.2 -I/usr/lib64/glib/include 
> -I/usr/X11R6/include -fno-merge-constants -fno-gcse-sm -c 
> ../uae_cpu/compiler/compemu_support.cpp -o 
> obj/compemu_support.o In file included from 
> ../uae_cpu/compiler/compemu_support.cpp:753:
> ../uae_cpu/compiler/codegen_x86.cpp: In function `void 
> raw_call(uint32)':
> ../uae_cpu/compiler/codegen_x86.cpp:3043: warning: cast from 
> pointer to integer of different size
> ../uae_cpu/compiler/codegen_x86.cpp: In function `void 
> raw_jmp(uint32)':
> ../uae_cpu/compiler/codegen_x86.cpp:3053: warning: cast from 
> pointer to integer of different size {standard input}: 
> Assembler messages:
> {standard input}:40547: Error: suffix or operands invalid for `push'
> {standard input}:40547: Error: suffix or operands invalid for `pop'
> make: *** [obj/compemu_support.o] Error 1
> 
> As for my previous report, pointers are welcome! BTW, has 
> _anyone_ gotten BasiliskII working on Fedora Core 3?
> 
> Matthias

Are you absolutely sure that you are using the newest code from CVS? I used
to have such problems with SheepShaver, not Basilisk some time ago, but it
has already been fixed (x86_64). Maybe only in SheepShaver code?

Jerzu