Executor is a Macintosh emulator that is able to run many ancient Mac OS 680x0 binaries (System 6 era, early System 7) without using any intellectual property from Apple Computer. Executor has not been actively worked on for many years. It is more of a curiousity than anything practical; it does not run PowerPC binaries, nor did it even run most System 7 applications. Unless you have a particular application that you know works with Executor, or just like emulation a lot, you probably don't want to spend any time with Executor. Included are a bunch of auxiliarly files and miscellaneous front-ends. The DOS port required various other libraries that we had permission to use, but that we did not necessarily have the permission to publish the source for, so the source to some of the packages that the DOS port requires is not present in the github repository. Don't be mislead by configure.ac, Executor currently builds using an ancient configuration script. If you want to try to build a version of Executor for Linux, try doing this (*After you've done a make install of syn68k): mkdir -p build/debug-linux cd build/debug-linux ../../util/configure.sh '--target=i486-linux' '--host=i486-linux' '--front-end=x' '--target-gcc=gcc' '--cflags=-fno-strict-aliasing -I/usr/X11R6/include -O0 -finline-functions -g -Wall' '--root=../..' '--target-file-format=glibc' '--sound=linux' '--syn68k-target=i486-linux-glibc' make That should leave you with a binary called executor. Unfortunately, without a System Folder, Executor won't even come close to running. If you're using a system that can install RPMs and you can dig up and install a copy of executor-aux-2.1pr16-1.i386.rpm, then you should be able to run. I'll fiddle around a bit and figure out the easiest way to build a System Folder for Executor from the git repository and add that info next. In the meantime, if anyone is reading this and wants a copy of executor-aux-2.1pr16-1.i386.rpm, try messaging me (ctm) at github. If you're on an x86_64 based machine and you have the ability to compile 32-bit binaries, you should be able to build a copy of Executor by doing something like mkdir -p build/debug-linux cd build/debug-linux ../../util/configure.sh '--target=i486-linux' '--host=i486-linux' '--front-end=x' '--target-gcc=gcc -m32' '--cflags=-fno-strict-aliasing -I/usr/X11R6/include -O0 -finline-functions -g -Wall' '--root=../..' '--target-file-format=glibc' '--sound=linux' '--syn68k-target=i486-linux-glibc' make However, you may find that you need to hand-edit Makefile and change the line HOST_GCC = gcc to HOST_GCC = gcc -m32 If you have SDL installed and would like to use the SDL-based version of Executor on Linux, you can try: mkdir -p build/debug-linux-sdl cd build/debug-linux-sdl ../../util/configure.sh '--target=i486-linux' '--host=i486-linux' '--front-end=sdl' '--cflags=-fno-strict-aliasing -I/usr/X11R6/include -O0 -finline-functions -g -Wall' '--root=../..' '--target-file-format=glibc' '--sound=sdl' '--syn68k-target=i486-linux-glibc' make If you have SDL installed and would like to play with the SDL-based version of Executor on Mac OS X Intel, you can try: mkdir -p build/debug-macosx-sdl cd build/debug-macosx-sdl ../../util/configure.sh '--target=i486-macosx' '--host=i486-macosx' '--front-end=sdl' '--cflags=-fno-strict-aliasing -I/usr/X11R6/include -O0 -finline-functions -g -Wall' '--root=../..' '--target-file-format=glibc' '--sound=sdl' '--syn68k-target=i486-macosx-glibc' make If you have SDL installed and would like to play with the SDL-based version of Executor on Mac OS X PPC, you can try the following. mkdir -p build/debug-macosx-sdl cd build/debug-macosx-sdl ../../util/configure.sh '--target=powerpc-macosx' '--host=powerpc-macosx' '--front-end=sdl' '--cflags=-fno-strict-aliasing -I/usr/X11R6/include -O0 -finline-functions -g -Wall' '--root=../..' '--target-file-format=glibc' '--sound=sdl' '--syn68k-target=powerpc-macosx-glibc' In the past it was possible to cross-compile a version of Executor for Windows using mingw32. So far that port hasn't been tried since putting the code on Github. It probably doesn't work, but probably could be made to work without much effort. My email address is still , although ARDI itself is defunct. I get a ridiculous amount of spam and will quite possibly not see email addressed to me. I'm ctm on github (http://github.com) and typically check my email there once a day. --Cliff Matthews