You can put it elsewhere if you want. The first step is to get the source code. The normal instructions see  include getting a copy of SDL the Simple DirectMedia Layer suitable for developing a program that links to an SDL library to do its user interface like making a window and getting events from the keyboard and mouse. There are two choices each with advantages and disadvantages. To get it:. Anyone using a computer with an Intel- or AMD-based CPU manufactured within the past 5 years needs to select whether they are compiling for "bit" or "bit".
In addition, the normal build scripts want to use the -g and -O2 options. To get this to happen we need to set some environment variables:. Alternately, you may put something in your. There is only one binary in SDL This gives two advantages: When prompted for a password, enter anoncvs.
You won't see what you're typing. Since I'm a Terminal geek I type:. Then to actually run BasiliskII remembering that I have already have another copy of BasiliskII working, so I've set up the preferences file, a boot drive image, etc. I can type:. Sometimes to rebuild just one module, I have to manually remove the object:.
macOS - Wikipedia
I did not find any need to do this, because SheepShaver's JIT compiler has already been fixed in a manner that addresses the JIT compiler temp register bug. I found that these messages are okay and do not indicate a significant problem. No such file or directory. This will happen if you switch from one SDL to another as I discuss above.
This is particularly prevalent on Snow Leopard systems, the first version of MacOS X in which bit building is the default, but where many users and developers try to keep some things in bit. I fixed this error by building everything with the target architecture explicitly specified. In my particular case I want everything to be a bit binary, so I choose the i architecture. The complete steps to build BasiliskII then become:. If you did not build SDL, but instead are trying to use the SDL that is installed by MacPorts or from some other type of software installation, you can also encounter the error:.
I got this on one of my Snow Leopard systems despite having installed SDL through MacPorts and building BasiliskII in the standard way, with configure supposedly solving any compatibility problems for me.
- font - How to emulate Mac OS 8 (in a way that supports CD-ROMs) - Ask Different?
- after effects cs6 serial key for mac.
- mac greeting card templates free?
- Basilisk II.
The issue is that I didn't have the "universal binary" version of SDL, and unfortunately configure is not able to handle this common problem. But if the output is missing the text " universal ", like this:.
If your SDL was installed through something other than MacPorts, you have to discover what it was compiled for manually. Begin with the command sdl-config --libs , which lists out the libraries in your currently-installed SDL. You'll get output like this I've broken it up into mutiple lines:. The two items ending in a ". Now use the command otool -vh [pathname] and look in the cputype column:.
Classic Mac OS
The presence of "I" in the cputype column indicates that this SDLlibrary is bit. Whatever type of SDL you have, the solution to the " If you launch BasiliskIIfrom the Finder you might see nothing, or perhaps a window appears briefly and immediately disappears: BasiliskII has crashed. The last two lines are an error. As it happens, BasiliskII's JIT compiler tries to "assemble" operations in a virtual machine like a into Intel x86 code by gluing together snippets of code corresponding to operations like "move this register to the stack" or "add this register to that register".
Each of these instructions is turned into one or more Intel machine language bytes by using the GCC compiler, at the time that you do the build. As it happens, the GCC compiler 4. However, with GCC 4. So instead of giving us something like:. The fix is to use the GCC 4. X11 error "cannot open display".
The ": If you see": You can also avoid this complication by going into the running X11 application, starting a new xterm window from its Applications menu, and launching BasiliskII. If you launch SheepShaver from a terminal shell , you'll see:. Apple decided way back in MacOS X I use Xcode 3.
I found the following suggestion at 2 , which might solve the problem:. If you've installed Xcode 4. To fix it, I did the following: It seems to me based on Google searches for this error that BasiliskII and SheepShaver are trying to use obscure cross-compilation features of the GCC compiler, which require certain runtime libraries, and these runtime libraries such as crt1.
I haven't tested either of these suggestions, because I have never had the "C compiler cannot create executables" problem.
Fixing nocdrom true on MacOS host. I found a fix to the problem that made it impossible to eject CD-ROMs if you have the preferences nocdrom flag set to true. For the original message and followup discussion, see this thread on the Emaculation forum posted on the 21 st April There has been a bug for many years that causes this setting to only partly work. Disk Utility tells you it can't be unmounted. As you can see, it does perform an appropriate test:.
Think of this as a more convenient way to access the software on an old Mac you already own, rather than a way of getting a whole extra virtual computer. Basilisk II can emulate a Macintosh Classic or a Macintosh II, and it can theoretically run operating systems all the way back to version 1.
- mac cosmetics nordstrom topanga mall;
- Welcome to Low End Mac.
- Hint Options!
- General information.
- nitro pro 8 for mac.
In practice, System 6 is usually the furthest back you need to go. Current page: How to run old software on your Mac. Page 1 of 2: Many of the old 8-bit games are still surprisingly playable. See more how-to articles.