Amiga.org
The "Not Quite Amiga but still computer related category" => Amiga Emulation => Topic started by: on March 21, 2003, 09:49:06 PM
-
Hi!
I try to compile UAE 0.8.22 under Redhat 8.0 like this:
sh configure
make
then it says this:
./tools/cpuopti cpufast.s
Corrupted assembly file!
Internal error; file /home/jan/uae-0.8.22/src/cpuopti.c, line 28
make[1]: *** [cpufast.s] Fehler 134
make[1]: Verlassen des Verzeichnisses Verzeichnis »/home/jan/uae-0.8.22/src«
make: *** [all] Fehler 2
i've read that it can solved with another compiler version, but how?
had anybody an idea?
please help
Kabaal.
-
I've had problems tinkering with 8.22 under Mandrake - even after getting the source RPM's and rebuilding / patching.
unless there is a particular feature you need (like running it SVGA), I'd suggest downloading the binary RPM and installing 8.21 (it's probably on one of your disks already) - I've got RPM's with and without the JIT compiler and both had bsd_socket option compiled already.
Siggy.
-
Linux Vampire?
There's a new one..
-
sorry, i mean compile, not vompile (hmpf :-x )
i installd the redhat rpm but it dont suport the fullscreen mode :-(
then i try the mandrake rpm. it runs in fullsreen but has no sound :-(
... if i can't take care of this i try to run winuae under a windows emulator :-P
-
Try compiling with an earlier version of GCC, such as 2.95.
Do something like this when configuring:
CC=gcc-2.95 ./configure
and remember to supply your configure options on the same line.
-
Sorry I didn't reply for a while... but here's something for you to look into:
In the directory you run UAE from (more than likely your home directory) look for a file called .uaerc
This is a config file that UAE will read it's config from.. in there you can turn on your audio.
Alternatively, boot UAE with it's interface (not full screen) - use the GUI to set up your configs till you're happy with them and save the config (.uaerc) and then boot full screen from there on in.
Personally I copied UAE to a local bin directory and wrote some shell scripts to set me up properly. I also put my home directory as a local drive, so to change config I load up a text editor, modify, reboot.
Never leave UAE.
(Hmm maybe I should write a little amiga GUI frontend for this.....)
Another interesting dirty trick.
Don't run UAE full screen at all (personal pref here, I don't like linux programs running as root).
Instead run with a minimal window manager - something like AmiWM -- or alternatively no WM at all. Boot up this configuration from a shell script (mine is simply called goami) -- setup UAE with the same screen res as you run Xwindows at.
Under Xwindows (with no WM) it looks as it if it is running at fullscreen - under AmiWm you have a 'Amiga screen bar' at the top of your screen (pull down that screen and have a Linux WB running behind it)..
Why would you do this? Well it all works together for the ultimate dirty trick:
Set up a crontab task and a shell script to check a subdirectory every minute or so (up to you how often) and execute whatever scripts it finds in there (this is why you DON'T run UAE as root -- and I'm currently working on a way to do this that isn't a security nightmare :P ) - make 'start scripts' for your fave 'can't live without' linux progs -- Your fave webrowser, xmms, whatever...
From the amiga side, make scripts that copy these "starters" to the "execution draw" and link them to icons (tool of your choice).
Result - you hit a button on your WB in UAE - 30 secs later you get Mozilla running.
If you use AmiWm, it's window sizing gadgets will look like WB 2.0 - so you're not distracted.
It's cheap, it's dirty, it's fun.
Siggy
-
first thx for your help.
i try to compile uae to set configs like "use sdl". so i have to compil it anyway.
i tryed it with this:
CC=gcc-2.95 ./configure
but now it says this:
loading cache ./config.cache
checking for gcc... gcc-2.95
checking whether the C compiler (gcc-2.95 ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
hmmm seemst that i dont have the right compiler version.
:-(
-
hmmm seemst that i dont have the right compiler version.
Unfortunately the uae's assembly optimizer doesn't work with the assembly output of gcc 3.x, so you either use gcc 2.95, or you just disable assembly optimization. You can do that easily by issuing this command, once the compilation stops:
cp cputmp.s cpufast.s
in the uae-/src directory, and then run "make" again.
-
cp cputmp.s cpufast.s
in the uae-/src directory, and then run "make" again.
Wow, thanks man, that was a direct hit!
I dont understand why :-o but uae runs now.
Thanks very mutch.
-
Cheers guys,
I accidentally tripped over this thread and now I'm glad I did.
I'm on my home RH8.0 system and was having exactly the same probs.
did the: CC=gcc-2.95 ./configure
and the: cp cputmp.s cpufast.s
Worked a treat. :-o
Cheers fellas.
Crumpster