PUAE 2.4.0 beta series

[GnoStiC]

PUAE 2.4.0 beta series:
http://github.com/GnoStiC/PUAE

* i don't supply binaries for any os
* this version works for me, macosx 10.6.7 on macbook pro i7 & imac
* for bug reports "Toni Wilen's rules" apply; "not working is not a bug report"
* don't forget to report bugs so that i can fix them (attach your config file and steps to reproduce the bug)

cheers,

[Mequa]

A question, Gnostic:

Given you're sticking to the WinUAE version numbers, how closely sync'd is PUAE to WinUAE?

[GnoStiC]

emulation corewise almost sync'd.
but not all these new features are in the gui menus, you have to hack your way around enabling them. i have to put them in the gui, test it, enable it.. i hope one day i'll have enough spare time to do it :)

A question, Gnostic:
Given you're sticking to the WinUAE version numbers, how closely sync'd is PUAE to WinUAE?



p.s.: 2.4.0 beta is not pushed to git yet, found some last minute bugs. will push tomorrow.

[palaste]

Thanks for the update! I will try to compile the newest version of the source code and see if it works any better. The last time I tried, it seemed like the problem was with Gnome, not with P-UAE.

[chiark]

...and here was me thinking you'd pretty much got PUAE to where you wanted to be :D

Excellent news, thanks GnoStiC!

[kire_online]

Eagerly awaiting binaries for Mac OS X from some generous person.

[chiark]

Once 2.4.0 is on github, I'll provide an experimental build.

I think we now have a stable 2.3.3, which I'll archive as 'stable' in the distro, and also 2.4.0 as experimental.

[Mequa]

I'd like to see a stable Ubuntu/Linux binary making it into the package manager alongside E-UAE.
WinUAE is one of the main reasons I stick to Windows 7 as my primary OS.

(That and Dolphin for Wii emulation, which is much slower on Linux).

[nexusle]

Hi chiark,

is there any mac build out now??

[chiark]

It's having trouble with P96 modes, but it is working. I'll post it later this weekend.

[dreamkatcha]

I'll look forward to that, thanks. Have you been compiling it with support for CD32 or is that not possible yet?

[nexusle]

Have you been compiling it with support for CD32 or is that not possible yet?

This is a good question! I think, it's a little bit trickier to get CD support working on Mac OS X build (the same thing on E-UAE).

If you want, you can try my E-UAE build with buildin CD ROM support (CD32 emulation is working)

http://dl.dropbox.com/u/46087535/e-uae_ub.zip

[dreamkatcha]

Cheers nexusle. I gave it a go and managed to get the boot screen to appear - so far so good. :)

[nexusle]

Please note. To get CD ROM working, you must start the emulator without CD ROM in drive.

[dreamkatcha]

Thanks for the tip. I thought I'd try it by mounting a CD with Toast to begin with, but EUAE doesn't want to play ball. Nevermind, back to old school CD burning.

[Daedalus]

Hi all, I asked in another thread but noticed afterwards that it was an old one (arrived there straight from Google...), but how difficult is this to build on Ubuntu? I'd like to give it a go, since E-UAE doesn't seem to behave well on my setup.

Of course, if someone had a binary package built that they could share, that would be easier ;)

[wilshy]

Loving your work as always!

[Mequa]

Has anyone had any luck getting AROS ROM working on PUAE?

I has no success using the latest available sources for PUAE 2.3.3, even when enabling the serial port during compilation and in .uaerc. It hangs at a blank screen when trying to run on Ubuntu/Kubuntu 11.10 with AROS ROM (I tried a few versions).

I tried using Kickstart 3.1 ROM and running the AROS boot ADF, and got this error:

Your Amiga program just did something terribly stupid 0092F028 PC=00000488
D0 0000FFFF D1 0000FFF8 D2 00000000 D3 00000000
D4 00000000 D5 00000000 D6 00000000 D7 00000000
A0 0092F028 A1 0000043E A2 001FFDB0 A3 00000000
A4 0000021C A5 00F80218 A6 0000020C A7 00000400
USP 00225938 ISP 00000400 SFC 00000000 DFC 00000000
CACR 00000000 VBR 00000000 CAAR 00000000 MSP 00000000
T=00 S=1 M=0 X=0 N=1 Z=0 V=0 C=0 IMASK=0 STP=0
Segmentation fault

That's using the aros-20110822-boot.adf image included with Amiga Forever 2012, which works with E-UAE.
Later versions (e.g. from latest nightly builds) give a garbled yellow screen instead (on both E-UAE and PUAE).

[Mequa]

CPU seems to be stuck in the GUI at 68000, despite showing up in the terminal window as 68020.

I also got this when pressing the pause button:
(UAE:23182): GLib-GObject-WARNING **: invalid cast from `GtkButton' to `FloppyFileEntry'
Segmentation fault

It also appears the random segfaults on starting are related to the GUI - if I disable the GUI in .uaerc they magically disappear.

[Mequa]

I finally managed to build Linux and FreeBSD binaries of PUAE 2.3.3 f2fc773 with JIT working.

On 64-bit Linux/FreeBSD, it appears the best option for building PUAE is to run a 32-bit distro in e.g. VirtualBox. (64-bit seems very buggy at the moment as well as lacking JIT).

PUAE-f2fc773 Linux binary (zip archive) (http://dl.dropbox.com/u/51441369/PUAE-f2fc773-bin-linux-x86.zip)
PUAE-f2fc773 FreeBSD binary (zip archive) (http://dl.dropbox.com/u/51441369/PUAE-f2fc773-bin-freebsd-x86.zip)

The Linux build tested fine on Kubuntu 11.10 x64 on Intel i7, and Ubuntu 11.10 x32 on an Intel Atom netbook. The BSD version tested fine on PC-BSD 9.0 x86. A working configuration file is included, as well as the build script I used, and PUAE documentation and Amiga files. I also included E-UAE for fallback.

Still no-go with AROS ROM, however, so drop in a kick.rom. It appears PUAE's serial port emulation is broken? The GUI is also still not fully operational, so edit the .uaerc file included as necessary (I also included a duplicate copy). It is very close to usable though! :D

Remember to change the file permissions to executable before using it.


Edit: It will boot the CD32 ROM too:
http://img830.imageshack.us/img830/5761/puaecd32.png

:)

[Daedalus]

@Mequa

Cool, I'll have to give that build a try on my Linux machines! Thanks :)

[Mequa]

SCSI is not working yet, so you can't actually play CD32 games on PUAE. It bombs if you set chipset mode to CD32, the above uses generic.

One fall-back solution I discovered for testing purposes is to run the e-uae binary from the same directory (now included). It will then use the same .uaerc configuration and do things currently broken in PUAE (such as boot CD32 games, work with AROS ROM and its "relokick" ADF, mounting directories without major bugs [HDFs still work in PUAE, make_hdf is included], and allow editing of the config file with a working GUI).

Caution: If you disable the GUI and set fullscreen mode in .uaerc, PUAE will indeed work in fullscreen, but you may find it *very* difficult to exit without powering off the PC!

One notable point regarding building: I built it on a 32-bit Ubuntu VM *without* hardware virtualisation and enabled GCC optimisations (and bsdsock support).


Update: I added E-UAE 0.8.29-WIP4 x86 binary to the archive to allow for easier fallback for testing (it's "./e-uae", PUAE is the default "./uae").

[Daedalus]

Cool, I'll bear that in mind! I'm really looking at using it for having an AmigaOS machine on the go, so CD32 support isn't that much of an issue. Picasso96 and JIT would be more useful for me anyway. E-UAE would probably do, were it not for how it decides to absolutely crawl after a few minutes for no apparent reason, so I'm hoping PUAE solves that issue for me...

[Daedalus]

@Mequa

Okay, I can't seem to get that build to boot. I'm using the included .uaerc file (updated for my setup). I haven't defined any hard drives or floppies, just the ROM. E-uae starts and shows the purple insert floppy screen as expected, but uae gets to the point where I'd expect the purple screen, but simply quits. Just as it does so, there's a small chirp from the speakers, similar to what you get with a corrupted MP3, i.e. digital noise. Any ideas?

Running it in the terminal, I get this line when it quits:


(UAE:5719): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed
Assertion 'pa_atomic_load(&e->pool->stat.exported_size) >= (int) b->length' failed at pulsecore/memblock.c:1106, function pa_memexport_process_release(). Aborting.
Aborted

[Mequa]

Try changing sound_interpol=sinc to sound_interpol=none if the error is with pulseaudio.
(Now updated in the archive's .uaerc, since sound interpolation seems unstable.)

First line looks like a GUI bug.

If that still crashes, try setting use_gui=yes to use_gui=no.
Also watch out for any duplicate settings.

[Mequa]

Update: I also did a FreeBSD x86 build of PUAE (tested on PC-BSD 9.0 x86), using the same build configuration file as for Linux, and included E-UAE as before:

PUAE-f2fc773 FreeBSD binary (zip archive) (http://dl.dropbox.com/u/51441369/PUAE-f2fc773-bin-freebsd-x86.zip)

:)

[mgandalf]

I'm trying to use my old Amiga RDB file, which works well under WinUAE and E-EAE with PUAE on OSX, but PUAE refuses to use the file. It's over 2gigs in size. Looking through gdb, and tracing the code, I see lseek() is being called from hardfile_unix.c:hdf_open_target(), but the return is size_t (?), which ends up being a large negative number in my case.

Shouldn't size_t be off_t instead? I've haven't tested my theory yet, as I have yet to compile my own PUAE.

- Mark.

[mgandalf]

I'm trying to use my old Amiga RDB file, which works well under WinUAE and E-EAE with PUAE on OSX, but PUAE refuses to use the file. It's over 2gigs in size. Looking through gdb, and tracing the code, I see lseek() is being called from hardfile_unix.c:hdf_open_target(), but the return is size_t (?), which ends up being a large negative number in my case.

Shouldn't size_t be off_t instead? I've haven't tested my theory yet, as I have yet to compile my own PUAE.

- Mark.

Ok, size_t is fine here. I was thinking of lseek(). It seems fseek() is 32bit only, and -D_FILE_OFFSET_BITS=64 has no effect. I replaced fseek() with fseeko() and ftell() with ftello() everywhere, and now the hardfile opens.

- Mark.

[GnoStiC]

@mgandalf:
fseeko64 is even better, you should also change (long)offset parameter.
i don't have such a big hdf so i never had any problems :)

[chiark]

You're back!

When are you going to push a 2.4.0 to Github? :)

[Mequa]

Welcome back, GnoStiC! Excellent news!

I need an incentive to make Ubuntu my primary OS on my dual-boot system. Right now thanks to WinUAE, Microsoft owns my soul. :)

[mgandalf]

@mgandalf:
fseeko64 is even better, you should also change (long)offset parameter.
i don't have such a big hdf so i never had any problems :)

By setting -D_FILE_OFFSET_BITS=64, all that should be taken care of. However, I've read xcode ignores it. I've also read off_t is 64bit.

I don't fseek64 or fseeko64 exist on osx (at least not on gcc 4.2).

- Mark.

[mgandalf]

Ok, on to the next issue. :) I've read where a few people are having issue with Picasso96 modes not showing up. I'm having the same issue.

My RDF file was used on E-EAE (Ubuntu) with Picasso96 working, but I verified all the P96 files were in place anyway. I've set my gfxcard_size to 8meg. My cpu_type is set to 68040. The output from puae looks promising, as it lists P96 modes available, but non show up in screenmode preferences.

Also, when I enable JIT by setting cache_size to 8meg, PUAE dumps pretty quickly with:

JIT_APPLE: can't handle access!
JIT: instruction byte 713984166 is 8b
JIT: instruction byte 713984166 is b7
JIT: instruction byte 713984166 is 08
JIT: instruction byte 713984166 is e0
JIT: instruction byte 713984166 is e4
JIT: instruction byte 713984166 is 16
JIT: instruction byte 713984166 is 0f
JIT: instruction byte 713984166 is ce
JIT: instruction byte 713984166 is 8b
JIT: instruction byte 713984166 is 2d

- Mark.

[Mequa]

I've noticed some signs of life at http://github.com/GnoStiC/PUAE

2.4.1 beta
commit 9aa5c89e61
GnoStiC authored 7 days ago

The latest version doesn't appear to be buildable yet though, but it seems there is still some work going on with PUAE. :)

[demether]

What about overall PUAE performance ? How is it compared to WinUAE ?

I' m running linux, and I'm not happy with e-uae or fs-uae for my purpose (emulating a high end classic amiga).

On e-uae, I always had some full screen modes problems (especially for native ecs-aga modes, for rtg/p96 it works OK), causing out of range lcd problems, or in the best case, displaying the games and demos on a tiny black window.


thanks !


edit : I tried to install it from a converted rpm file on my mint linux PC, it's working BUT :

no uaer config file in /home
saving new config file does not work
if I try using a .uaerc (putting it by hand in /home), puae does not launch

[Philantrop]

demether, you do realise that fs-uae can emulate a high end classic Amiga just as well as a plain old Amiga 500?

Emulation-wise, fs-uae can do everything puae can and more.

[FrodeSolheim]

demether, you do realise that fs-uae can emulate a high end classic Amiga just as well as a plain old Amiga 500?

Emulation-wise, fs-uae can do everything puae can and more.

Except the one thing demether is especially interested in, namely JIT (http://eab.abime.net/showthread.php?t=64014)! (Of course, with a modern fast CPU, such as an i7, the emulated Amiga in fastest-possible-mode is fast even without JIT, but not as fast as it would be with JIT). I am considering adding JIT (for x86), but it is not at the top of my todo-list.

[Philantrop]

Frode, implement JIT for x86_64 and eternal fame among the Amiga emulation scene will be yours! ;)

[demether]

@philantrop :

Try to run FS-uae on an old athlon 2400+ 1gb nvidia gfx5600 128mb to emulate a 68040 fastest speed amiga and you'll see what I mean :D

I know the potential of fs-uae, I saw for example the scaling integration wich is really great. No question about the software quality.

But it stills too slow by fair comparison (trying each system, using 060 demos as benchmark) with winuae JIT enabled or even e-uae JIT enabled for my needs (= running 060 demos and use production tools on os3.x).

I want to create a sort of "x86 amiga". A pc able to boot and run amigaOS 3.x, without seeing the host OS behind. For now, and compared to my needs and available hardware, only windows XP + winuae can (sadly) do the trick. I'd like to install a minimal linux + fs-uae jit enabled, one day, since I'm pretty sure it will be at least as good, probably better.



@FrodeSolheim :

You perfectly understood my needs :great

[Mequa]

Frode, implement JIT for x86_64 and eternal fame among the Amiga emulation scene will be yours! ;)
Now THAT would be non-trivial!

And there's ARM and PPC too. :spin

[GnoStiC]

now that fs-uae is out (and i believe it'll have JIT soon), you'd better go with it :)

[nexusle]

Is this the dead of PUAE?!

[GnoStiC]

nope i'll always work on Amiga Emulation one way or another..

but let's be honest, fs-uae provides what most amiga emulator users need and more. and i believe at one point Frode will also code a nice polished GUI for advanced users :)

Is this the dead of PUAE?!

[demether]

nope i'll always work on Amiga Emulation one way or another..

You can take a look on aros classic amiga emulation/integration if you don't know what to do :D:great

[dreamkatcha]

GnoStiC, just wanted to add that despite the existence of FS-UAE I really appreciate the work you've put into PUAE and hope you continue to improve it in future.

As demether said, PUAE remains the better solution for Amiga emulation on low-end computers.

[lesta_smsc]

Kudos to your hard work Gnostic! PUAE reminded me of Fellow... ran very well on older machines! :)

[Mequa]

but let's be honest, fs-uae provides what most amiga emulator users need and more.
While I appreciate the hard work Frode has put into FS-UAE, from what I've seen it's not a feature-complete implementation of UAE but has several features removed. I'm not sure if newer versions of FS-UAE intend to have full WinUAE-like functionality, but from my impression PUAE was meant to bring the full feature set of WinUAE to non-Windows platforms, while FS-UAE focuses on a smaller feature set.

As such, I'd like to see a feature-complete updated non-Windows-only UAE, whether based on PUAE or FS-UAE. So I think PUAE development could fill this void, if Frode prefers to keep FS-UAE features limited for compatibility/gaming/media centre-like use.

There certainly seems room for both UAE's, so I hope FS-UAE development doesn't discourage further work on PUAE. Perhaps both could exchange sources (as well as building on WinUAE of course) to speed up development?

[ipp0]

Mhh. I never got P-UAE compiling. Now Version 2.4.1 gives me:make all-am
make[4]: Entering directory `/home/ipp0/Desktop/GnoStiC-PUAE-9aa5c89/src/gui-qt'
g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src/include -I../../src -I../../src -I../.. -I/usr/lib/qt4/include -I/usr/lib/qt4/include/QtCore -I/usr/lib/qt4/include/QtGui -I/usr/lib/qt4/mkspecs/default -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -DCPUEMU_0 -DCPUEMU_11 -DCPUEMU_12 -DCPUEMU_20 -DCPUEMU_21 -DCPUEMU_31 -DMMU -DFPUEMU -DUNALIGNED_PROFITABLE -DJIT -DAMAX -DGAYLE -DNCR -DAGA -DAUTOCONFIG -DFILESYS -DSCSIEMU -DSCSIEMU_LINUX_IOCTL -DA2091 -DCDTV -DCD32 -DBSDSOCKET -DSUPPORT_THREADS -DUSE_SDL -DFDI2RAW -DDEBUGGER -DSAVESTATE -DENFORCER -DACTION_REPLAY -DXARCADE -DDRIVESOUND -I../../src/include -I../../src -I../../src -g -O2 -MT puae_mainwindow.o -MD -MP -MF .deps/puae_mainwindow.Tpo -c -o puae_mainwindow.o puae_mainwindow.cpp
puae_mainwindow.cpp: In member function »void puae_MainWindow::display_fromselect(int, int*, int*, int)«:
puae_mainwindow.cpp:884: Warnung: NULL in Arithmetik verwendet
puae_mainwindow.cpp: In member function »void puae_MainWindow::values_to_memorydlg()«:
puae_mainwindow.cpp:1052: Fehler: »struct uae_prefs« hat kein Element namens »gfxmem_size«
puae_mainwindow.cpp: In member function »void puae_MainWindow::enable_for_memorydlg()«:
puae_mainwindow.cpp:1202: Fehler: »struct uae_prefs« hat kein Element namens »gfxmem_size«
puae_mainwindow.cpp:1203: Fehler: »struct uae_prefs« hat kein Element namens »gfxmem_size«
puae_mainwindow.cpp: In member function »void puae_MainWindow::values_from_sounddlg()«:
puae_mainwindow.cpp:1940: Warnung: NULL in Arithmetik verwendet
puae_mainwindow.cpp:1946: Warnung: NULL in Arithmetik verwendet
puae_mainwindow.cpp:1952: Warnung: NULL in Arithmetik verwendet
make[4]: *** [puae_mainwindow.o] Fehler 1
make[4]: Leaving directory `/home/ipp0/Desktop/GnoStiC-PUAE-9aa5c89/src/gui-qt'
make[3]: *** [all] Fehler 2
make[3]: Leaving directory `/home/ipp0/Desktop/GnoStiC-PUAE-9aa5c89/src/gui-qt'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/home/ipp0/Desktop/GnoStiC-PUAE-9aa5c89/src'
make[1]: *** [all] Fehler 2
make[1]: Leaving directory `/home/ipp0/Desktop/GnoStiC-PUAE-9aa5c89/src'
make: *** [all-recursive] Fehler 1
[ipp0@Oma-Rheinholz GnoStiC-PUAE-9aa5c89]$"Fehler" is german translation of Error.

Even ./configure && make gives me loads of errors.

[Mequa]

I get the same errors (in English!). It appears gfxmem_size is not implemented yet, among other things...

[stainy]

How will this work/compile for the Pandora??

[GnoStiC]

make[4]: Entering directory `/home/ipp0/Desktop/GnoStiC-PUAE-9aa5c89/src/gui-qt'
..


i never finished gui-qt. the only compilable gui at the moment is cocoa gui.


How will this work/compile for the Pandora??

check gp32x forums :)

[FrodeSolheim]

While I appreciate the hard work Frode has put into FS-UAE, from what I've seen it's not a feature-complete implementation of UAE but has several features removed. I'm not sure if newer versions of FS-UAE intend to have full WinUAE-like functionality, but from my impression PUAE was meant to bring the full feature set of WinUAE to non-Windows platforms, while FS-UAE focuses on a smaller feature set.

I would say that is has not yet added all features, rather than having some "removed" ;). But I don't intend to create a WinUAE clone, and I see little value in trying to recreate 100% the same feature set, just for the sake of it. Rather, I'll focus on adding useful or interesting features, whether they can be ported from WinUAE, some other UAE, or created from scratch. FS-UAE also has features which are not present in WinUAE. If you miss a specific feature in FS-UAE, you are welcome to make a feature request (http://eab.abime.net/showthread.php?t=63808).

As such, I'd like to see a feature-complete updated non-Windows-only UAE, whether based on PUAE or FS-UAE. So I think PUAE development could fill this void, if Frode prefers to keep FS-UAE features limited for compatibility/gaming/media centre-like use.

What features FS-UAE includes (and will include) is mostly based on considerations such as what I have time to implemented, what I want to implement, and what features I think I'll manage to maintain over time (Also, I have occasionally been persuaded by what other people think is important).

And yes, I primarily designed FS-UAE to scratch my own itch, to play Amiga games well on Linux actually. But FS-UAE has now several features which are not relevant for gaming, such as RTG graphics and upcoming JIT compiler support, so the scope has effectively been broadened.

It is also a misconception that FS-UAE is primarily designed for media centre setups (Partially my own fault of course, because of the initial project description on the webpage). I use FS-UAE mostly on my PCs in front of me. The GUI is designed to also work from 3 meters away, because I also want FS-UAE to work great in this setting, and I'm not interested in maintaining several different integrated UIs.

There certainly seems room for both UAE's, so I hope FS-UAE development doesn't discourage further work on PUAE. Perhaps both could exchange sources (as well as building on WinUAE of course) to speed up development?

All UAE projects are open source and license compatible, so source code is easily exchanged where applicable. -And the core emulation code is largely shared. I use the codebases from WinUAE, E-UAE, UAE and PUAE as reference points when working on emulation-related code (such as JIT) in FS-UAE. A lot of code is not easily shared however, such as the win32-specific code from WinUAE (od-win32), the QT GUI from PUAE, and the GUI for FS-UAE. There are opportunities for better code sharing in some places.

Anyway, I don't want to hijack this thread, just wanted to respond to the FS-UAE bits :)

[Harry]

I just retrieved PUAE from the repository, and I dont know how to build it. The compiling instructions say that i should run configure, but there is no configure in the package and also no instruction how to create it. Can you please either add a configure or the instruction how to generate it?

[Mequa]

I just retrieved PUAE from the repository, and I dont know how to build it. The compiling instructions say that i should run configure, but there is no configure in the package and also no instruction how to create it. Can you please either add a configure or the instruction how to generate it?
To generate the configure file, run ./bootstrap.sh

You may need to install some dependencies first, look at docs/compiling.txt for information. On Ubuntu/Mint you may need to use sudo before each line using apt-get...

For running configure, it may be best to do this from a script due to all the options. There are several included for this purpose, such as ./bronx_.sh , the main one used to build PUAE. You may wish to make a copy of this (or another script) and edit it to get the options you want, e.g. saving as "custom.sh" (then run "./custom.sh" from a Terminal).

These scripts also run ./bootstrap.sh and make, so a script like that should be all you need once the dependencies are installed. (Don't worry if you already ran bootstrap.sh.)

You may need to use sudo to get admin privileges (e.g. "sudo ./custom.sh", after following the above).

I'm not sure if the current repository version is buildable though, it may stop with errors. In that case, try obtaining an older version (and/or wait for an update).

Good luck! :D


Edit:
Below is my attempt to build the latest PUAE (GnoStiC-PUAE-129480a), using Ubuntu 12.04 32-bit (in VirtualBox). I have some experience with C code, but nothing like with projects as large as UAE! (Other than a small optimised routine I submitted for Akiko C2P, which is in WinUAE, PUAE and FS-UAE sources now...)

The current version fails with the following error message:
gtkui.c: At top level:
gtkui.c:2222:6: error: conflicting types for ‘gui_fps’
../../src/include/gui.h:15:13: note: previous declaration of ‘gui_fps’ was here

On modifying gtkui.c, I get this error:
gtkui.c: In function ‘set_mem_state’:
gtkui.c:335:19: error: ‘struct uae_prefs’ has no member named ‘gfxmem_size’

gtkui.c: In function ‘p96size_changed’:
gtkui.c:734:18: error: ‘struct uae_prefs’ has no member named ‘gfxmem_size’

I set the first line to 0 instead of gfxmem_size, and commented out the second.

It built for a while, then I got this error:
blkdev.c:125:3: error: ‘devicefunc_cdimage’ undeclared here (not in a function)
blkdev.c:191:2: error: #else without #if
blkdev.c:198:13: error: redefinition of ‘install_driver’
blkdev.c:135:13: note: previous definition of ‘install_driver’ was here
blkdev.c:204:2: error: #endif without #if

I replaced the reference to devicefunc_cdimage to NULL, and added "'#if 1" before the "#else".

Then later on when building again, I get:
akiko.o: In function `akiko_reset':
........../akiko.c:1819: undefined reference to `Sleep'

I commented out that line (which appears to be Windows-specific) and replaced with ";".

And it finally built! Screenshot below.

(AROS ROM isn't working though, as with the last build of PUAE.)


P.S. GnoStiC, please fix the above errors! :)

[GnoStiC]

1) i haven't touched gtk sources in a long time now, i'll fix those
2) for aros you've to supply extra -I /dev/ttysX command line parameter

i have newer sources on my other pc, i'll commit them in a day or two.


...
(AROS ROM isn't working though, as with the last build of PUAE.)
...
P.S. GnoStiC, please fix the above errors! :)

[Mequa]

As for gtk, you may also want to take a look at these warnings on running ./uae binary from a Terminal:

(UAE:10870): GLib-GObject-WARNING **: invalid cast from `GtkFrame' to `GtkBox'

(UAE:10870): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed

(UAE:10870): GLib-GObject-WARNING **: invalid cast from `GtkFrame' to `GtkBox'

(UAE:10870): Gtk-CRITICAL **: gtk_box_pack: assertion `GTK_IS_BOX (box)' failed

1) i haven't touched gtk sources in a long time now, i'll fix those
And also blkdev.c and akiko.c (if you haven't fixed those already)?

2) for aros you've to supply extra -I /dev/ttysX command line parameter
With ./configure or make, or puae binary? (Or another way?)

I also get this when running the binary from a Terminal:
Could not load system ROM, trying system ROM replacement.zfile_gunzip: aros.gz failed. not gzipped file.

[Brian_S]

Hi GnoStiC,

I see you have got PUAE running on a Raspberry Pi. I started trying to compile the latest git master, but it's full of errors which I'm ploughing through - I'm compiling on the debian 6 image from the Raspberry Pi foundation and using the build_linux_nojit.sh script slightly modified to include --with-sdl-gui.

There seem to be lots of mis-matched prototypes that have needed tidying up.

Do you have a more recent set of sources that could be commited to github?

Very eager to get PUAE running on my pi! :D Thanks so much for the software!

[Brian_S]

Okay, back-tracked to 2.3.3 rather than bleeding edge and everything compiled fine using SDL-1.2.15 on the raspberry-pi. It runs good, but is definitely a bit slow. It's not too bad, but it's definitely slower than your video shows!

Can you let me know what options you used to compile? Did you enable JIT?

Anyway, very glad to get PUAE running on the pi! Yay! Thanks so much for this software! :D

[marlo]

Hi all, im new to this forum but not for Amiga, from early days (i have 51) I have installed on a chinese android tablet Puae 2.3. I dont know nothing about programming in android /linux/ubuntu. So i only need where can i get tha last Puae version in .apk format to install in my tablet. Thanks to all for any help.

[spannernick]

Does this work on COS 32bit..?

[Rissol]

Hi,

Im on Lion 10.7.4, may anyone compile the latest P-UAE, plz ? i really dont know how to do it, would be nice if anyone make it avaiable.

Thanks :)

[chiark]

unfortunately P-UAE will not build on my machine anymore, so I'm unable to provide binaries. :(

[Mequa]

unfortunately P-UAE will not build on my machine anymore, so I'm unable to provide binaries. :(

Same issue here on Linux.

[chiark]

Well, I've just retried, and it seems things now compile - GnoStiC made some changes to the package and it now does compile quite happily on Xcode 4.2

Will post a binary later :D

[nexusle]

Cool!

[marlo]

Great!!! Please upload an Android version if is possible!!!

[nexusle]

Sorry, he build only versions for Mac OS X

[chiark]

Yup, OSX only I'm afraid... I'll try to sort it out today/tomorrow - apologies for the delay.

[chiark]

http://www.binarydevotion.com/?p=198
:D

Version 2.4.2. I'll build a 2.5 when it's a little more stable...

[nexusle]

Does this mean GnoStiC is still working on PUAE?

[chiark]

Oh absolutely! It looks very much like there's a 2.5 version in the works following Tony's work...

[Methanoid]

@Chiark

Would it be possible to (next question is "would you, please") compile PUAE for iOS. I am actually thinking primarily ATV2.

Before you think I am some nutter... I'll explain

ATV2 mega low power consumption - I never switch my 2 off!
ATV2 is cheap
ATV2 with a good UAE (with HD support, bsdsocket.library support etc) you could run an Amiga BBS under emulation (better than leaving a PC on 24/7)

More Amiga BBS could be available (largely for nostalgia reasons)

OK I admit I am mad...

But possible?

[chiark]

Sorry, I don't have an ATV2 and I'm not really terribly interested...
Is it possible? I would think so given that I've compiled EUAE for a Sharp Zaurus... but a new UI would be needed.

I am interested in Raspberry Pi though, which is ARM based...

[Methanoid]

OK, Pi will do.. I have one of them :)