PearPC is an architecture independent PowerPC platform emulator capable of running most PowerPC operating systems. The following operating systems were tested and run (to some extend) under PearPC: Mandrake Linux 9.1 for PPC: Runs very well Darwin for PPC: Runs well Mac OS X 10.3: Runs well with some caveats OpenBSD for PPC: Crashes while booting (accesses PCI in an unsupported way) NetBSD for PPC: Crashes while booting PearPC simulates the following hardware: CPU: Sort of G3, no altivec yet. Includes a minimalistic debugger. The CPU is completely deterministic, optimal for OS-development. CPU JITC-X86: A very fast CPU for x86 systems that translates the PowerPC code on-the-fly to native code. Still a little bit experimental. PCI-Brige: A barebone PCI-Bridge, enough to work with. IDE-Controller: Sort of CMD646 with bus-mastering support. You can attach IDE-Harddisk(s) and/or IDE-CDROM(s) (represented through files or devices on the host). PIC: A programmable interrupt controller (sort of Heathrow). VIA-Cuda: With attached Mouse and Keyboard. Network Controller: Emulates a 3COM 3C90x, works currently only on POSIX with /dev/tun support. NVRAM: Capable of storing 8KiB non-volatile memory. USB: A non-usable USB-hub, but enough to make the OS think that there is an USB-hub. PROM: Sort of openfirmware. Ugly and contains a lot of hacks, but enough to support Yaboot and BootX and to boot from HFS/HFS+ partitions. Reproducible: Always Steps to Reproduce:
Created attachment 31092 [details] pearpc-0.1.ebuild
Created attachment 31104 [details] pearpc-0.1.ebuild .) video.x also gets installed .) ppccfg.example patched to point to video.x .) added local USE-Flag "jit"
Created attachment 31448 [details] pearpc-0.1.1.ebuild No changes to the ebuild - just a version bump - tested and worked fine for me so thought I'd upload it. Thanks Thomas for the original ebuild.
Thanks a lot. I'm going to get ahead of Gentoo and install it right now. ;) I miss Escape Velocity and Hearts Deluxe!
Double version bump 0.1.1 and 0.1.2 versions came out.
Created attachment 31781 [details] pearpc-0.1.2.ebuild pearpc 0.1.2 ebuild
You also might want to consider that adding a new use flag is unnecessary and that you can specify to use jitc when make keyword is x86. As i seem to remember from pearpc website, jitc only works so far on x86 arch. So the use flag would be useless on other archs beside x86. I will test later tonight on my mips box to see if it compiles and at least load up osx. An example: [ "`use x86`" ] && --enable-cpu=jitc_x86 this of course, forces x86 people to use jitc, but that is probably good, better to be 40times slower than 400 time slower without jitc.
Why is this assigned to the PPC Porters? Isn't this application more useful on non-PPC hardware?
There is also a pre-0.2 version available too with better athlong 64 support. Could someone possibly create an ebuild for the pre-0.2 or cvs?
I tested the 0.1.1 and 0.1.2 ebuilds, they work fine without error. I think that the jitc useflag should be there (or some kind of similar solution) since it does not work on all x86 machines. Should be ready for portage soon.
Why would PPC care about a PPC-emulator that only has a JIT-compiler for x86? ;)
*** Bug 52827 has been marked as a duplicate of this bug. ***
How about PearPC's SDL-teams efforts? Their site deliver .tar.bz2-files within somekind of counter-script: http://www.richardgoodwin.com/pearpc/sdlbuilds.php. From what I read on http://www.pearpc.net it should boost pearpc alot (haven't tested it yet myself, still waiting for MacOSX to finish :>)
Using the 0.1.2 ebuild, USE="X -qt", Configure fails: checking for c++... g++ checking whether the C++ compiler (g++ -D_FILE_OFFSET_BITS=64 -pipe -g -O2 -Wall -fsigned-char -fomit-frame-pointer ) works... yes checking whether the C++ compiler (g++ -D_FILE_OFFSET_BITS=64 -pipe -g -O2 -Wall -fsigned-char -fomit-frame-pointer ) is a cross-compiler... no checking whether we are using GNU C++... yes checking whether g++ accepts -g... yes checking for bison... bison -y checking how to run the C preprocessor... gcc -E checking for flex... flex checking for flex... (cached) flex checking for yywrap in -lfl... yes checking lex output file root... lex.yy checking whether yytext is a pointer... yes checking for ar... /usr/bin/ar checking for gar... (cached) /usr/bin/ar checking whether QTDIR environment variable is set... no configure: error: QTDIR must be properly set. !!! ERROR: app-emulation/pearpc-0.1.2 failed. !!! Function econf, Line 365, Exitcode 1 !!! econf failed zidane root # emerge info Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.6-mm4) ================================================================= System uname: 2.6.6-mm4 i686 AMD Athlon (TM) Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-tbird -O3 -pipe -funroll-loops -fomit-frame-pointer -mmmx -m3dnow" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache digest fixpackages sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X acpi alsa apm avi berkdb cdr crypt cups divx4linux doc dvd emacs encode esd foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 imap imlib java jpeg libg++ libwww mad maildir mikmod mmx motif mpeg ncurses nls offensive oggvorbis opengl pam pdflib perl png python quicktime readline ruby sdl slang spell sqlite ssl svg svga tcpd truetype unicode usb x86 xml2 xv zlib"
i DO want that!!!
Created attachment 33421 [details] pearpc-0.2.0.ebuild Another version bump to pearpc 0.2.0
Hi Devs, Is there any reason why this ebuild isn't making it into portage tree - is it just that it is such alpha software or is there something missing from the ebuild. Regards, Mark
I'm just waiting for it to stabilize a little. I'll probably commit 0.2.0 tomorrow.
In CVS, thanks everyone.
