Mac OS X 10.6.5 notes:Xcode: 3.2.3 64-bit Xcode IDE: 1688.0, Xcode Core: 1691.0, ToolSupport: 1591.0The configure line I used was:    CC='gcc -m32 -fno-stack-check -fno-stack-protector' OBJC='gcc -m32 -fno-stack-check -fno-stack-protector' ../../src/configureI'm using the version of syn68k that I built from my ancient_hackagebranch.========================================================================Executor is a Macintosh emulator that is able to run many ancient MacOS 680x0 binaries (System 6 era, early System 7) without using anyintellectual property from Apple Computer.Executor has not been actively worked on for many years.  It is moreof a curiousity than anything practical; it does not run PowerPCbinaries, nor did it even run most System 7 applications.  Unless youhave a particular application that you know works with Executor, orjust like emulation a lot, you probably don't want to spend any timewith Executor.Included are a bunch of auxiliarly files and miscellaneous front-ends.The DOS port required various other libraries that we had permissionto use, but that we did not necessarily have the permission to publishthe source for, so the source to some of the packages that the DOSport requires is not present in the github repository.If you want to try to build a version of Executor, try this:  cd src  autoreconf --install  cd ..  mkdir build  cd build  ../src/configure  make  make installThat should leave you with a binary called "executor" (at least on32-bit x86 Linux systems, or a Mac (Intel or PowerPC) with XCode 3installed) and a directory called "skel".  By default, executor willbe installed in "/usr/local/bin" and skel will be installed in"/usr/local/share/executor".skel itself isn't meant to be written to; it's meant to be copiedsomewhere and for the copy to be read/write.  For example,  cp -Rp /usr/local/share/executor/skel/volume /tmp/ExecutorVolume  export SystemFolder="/tmp/ExecutorVolume/System Folder"  executorThe environment variables that drive Executor including where Executorlooks for the system folder are a bit arcane and meant to fit togetherwith installers that we no longer use.  It may make sense to make itso that Executor automatically copies the contents of skel/volume to ausers home-directory the first time Executor is run, but that's anexercise left to the reader.If you're on an x86_64 based machine and you have the ability to compile32-bit binaries and you have these packages installed (where the ? is 3 forFedora 10, 5 for Fedora 11 and 6 for Fedora 12):  SDL-devel.i?86  libX11-devel.i?86  db4-devel.i?86  libXext.i?86  libXrender.i?86  libXrandr.i?86you should be able to build a copy of Executor by overriding CC andOBJC to be the 32-bit version and explicitly stating that you'rebuilding on a 32-bit system (which is a little bit untrue, but works):  mkdir -p build/debug-linux  cd build/debug-linux  CC='gcc -m32' OBJC='gcc -m32' ../../src/configure --build=i686-pc-linux  makeThe above works on Fedora 10, 11 and 12 x86_64.Yes, the above is pretty messy.  Since the x86_64 bit native version ofExecutor doesn't build and is likely to anytime soon, it probably makessense to make it so that by default we build the ix86 version of Executorwhen compiling on x86_64, and that we complain if the various 32-bitlibraries aren't available.In the past it was possible to cross-compile a version of Executor forWindows using mingw32.  So far that port hasn't been tried sinceputting the code on Github.  It probably doesn't work, but probablycould be made to work without much effort.At one time we had Executor running on the Alpha, a 64-bitenvironment.  We actually modified gcc to support "pointer bit-fields"and were able to get Executor to run.  Now that 64-bit machines aremore popular, I've begun an experiment in supporting 64-bit machineswithout modifying the compiler.  See README.64 for more info.As I continue Executor's transition to a recent gnu build system I mayinadvertantly push versions that don't build when using the abovecommands.  Don't hesitate to ask me if you're having troublecompiling, linking or running any of the above platforms.My email address is still <ctm@ardi.com>, although ARDI itself isdefunct.  I get a ridiculous amount of spam and will quite possiblynot see email addressed to me.  I'm ctm on github (http://github.com)and typically check my email there once a day.--Cliff Matthews