Has anyone gotten an Intel OS X 10.4.11 VM running?

[pipetogrep]

Hi all,

I have an idea for building Macports more quickly for PowerPC. It appears one can pass a "+universal" flag https://trac.macports.org/wiki/Universal to build for both PowerPC and Intel. My thought is, if I can get Tiger running in a VM on a modern machine, I'll be able to make builds that work for PPC and I can give my poor G4 Gigabit a respite from compiling for a week straight every time I do a new Macports install. This would really help with keeping the Tenfourfox Dev Toolkit updated more frequently.

Problem is, I'm struggling with getting a function Intel Tiger VM going. I did find and get this running https://archive.org/details/mac-os-x-10.4-tiger-for-intel-x-86-bootable-and-installable_202110 but it's 10.4.1 and does not appear to be update-able. I am curious if anyone has tried this or happens to have a virtualbox or qemu (intel) setup I could use as a starting point.

Any help would be appreciated! Thanks!

 

[pipetogrep]

Going to try this one next https://archive.org/details/xxxosx8610point4point11rev2_202007. Referenced from https://www.insanelymac.com/forum/topic/75841-xxx_os_x86_10411_install_disc_intel/

 

[Amethyst1]

Yes, use Tiger Server 10.4.7, which is universal to begin with, as base OS. It’s on the Garden. And this howto.

Forget those hacked-to-hell-and-back Hackintosh distros.
Forget 10.4.1, it’s a dead-end unless you have one of the Pentium 4–based DTKs.

 

[pipetogrep]

Yes, use Tiger Server 10.4.7, which is universal to begin with, as base OS. It’s on the Garden. And this howto.

Forget those hacked-to-hell-and-back Hackintosh distros.
Forget 10.4.1, it’s a dead-end unless you have one of the Pentium 4–based DTKs.

Ah nice. I'll give it a try. Thanks!

 

[joevt]

Also this thread: https://forums.macrumors.com/thread...on-a-modern-intel-mac-virtualization.2162582/

 

[repairedCheese]

You could always try VMware. It's, well, VMware, but with a little unlocking, it does work fairly well with basically no special setup needed. No graphics acceleration, but that shouldn't be an issue for your needs.

GitHub - paolo-projects/unlocker: VMware Workstation macOS

VMware Workstation macOS . Contribute to paolo-projects/unlocker development by creating an account on GitHub.

github.com

 

[barracuda156]

Hi all,

I have an idea for building Macports more quickly for PowerPC. It appears one can pass a "+universal" flag https://trac.macports.org/wiki/Universal to build for both PowerPC and Intel. My thought is, if I can get Tiger running in a VM on a modern machine, I'll be able to make builds that work for PPC and I can give my poor G4 Gigabit a respite from compiling for a week straight every time I do a new Macports install. This would really help with keeping the Tenfourfox Dev Toolkit updated more frequently.

I strongly advise not to use +universal on anything PowerPC. This is a can of worms, keep it sealed

Unless, of course, you are interested to help us fix universal builds, that would be awesome. But, AFAICT, it is a) non-trivial and b) gonna require enormous amount of time investment and significant changes to Macports.
In short, you can build universal as long as you can get away with gcc-4.* (to be honest I have no idea if apple-gcc-4.2 port supports universal builds correctly, but let’s assume it does; on Leopard you just use Xcode gcc-4.2). Even then, it is likely something will not build. Once you need C11/++11, everything breaks down, since gcc does not support building FAT binaries (driver-driver is needed).

Macports has a tool to make it work in principle (muniversal PGs), but a) it does not always reliably work even with Intel, b) cross-family builds are a pain, c) most of the ports do not use muniversal PG, which means they cannot be built as universal; you may try adding it locally, but you are likely to be on your own there.

You could build in Rosetta, however, for ppc (without universal). Just set the build_arch to ppc in macports.conf. I never tried that on 10.4–10.5, but it should work, I think. On 10.6.8 it does work, though you gonna need a few fixes from my branch.

 

[barracuda156]

If you will be okay with 10.5, there is this: https://github.com/catap/macos-ansible-playbooks

 

[pipetogrep]

I strongly advise not to use +universal on anything PowerPC. This is a can of worms, keep it sealed

Unless, of course, you are interested to help us fix universal builds, that would be awesome. But, AFAICT, it is a) non-trivial and b) gonna require enormous amount of time investment and significant changes to Macports.
In short, you can build universal as long as you can get away with gcc-4.* (to be honest I have no idea if apple-gcc-4.2 port supports universal builds correctly, but let’s assume it does; on Leopard you just use Xcode gcc-4.2). Even then, it is likely something will not build. Once you need C11/++11, everything breaks down, since gcc does not support building FAT binaries (driver-driver is needed).

Macports has a tool to make it work in principle (muniversal PGs), but a) it does not always reliably work even with Intel, b) cross-family builds are a pain, c) most of the ports do not use muniversal PG, which means they cannot be built as universal; you may try adding it locally, but you are likely to be on your own there.

You could build in Rosetta, however, for ppc (without universal). Just set the build_arch to ppc in macports.conf. I never tried that on 10.4–10.5, but it should work, I think. On 10.6.8 it does work, though you gonna need a few fixes from my branch.

Noted and thanks. I’ll give up. I don’t have the time or skill for this at this point in my life.

I appreciate you saving me the time and effort.

 

[barracuda156]

Noted and thanks. I’ll give up. I don’t have the time or skill for this at this point in my life.

I appreciate you saving me the time and effort.

If you still have the PowerMac from your signature (Dual 1.8 GHz Sonnet Encore), that should be decent to build from source natively. Huge stuff gonna take a while still, but otherwise it should not be a pain.
I have Dual 2.3, and it feels generally okay.

 

[Wowfunhappy]

I strongly advise not to use +universal on anything PowerPC. This is a can of worms, keep it sealed

Unless, of course, you are interested to help us fix universal builds, that would be awesome. But, AFAICT, it is a) non-trivial and b) gonna require enormous amount of time investment and significant changes to Macports.
In short, you can build universal as long as you can get away with gcc-4.* (to be honest I have no idea if apple-gcc-4.2 port supports universal builds correctly, but let’s assume it does; on Leopard you just use Xcode gcc-4.2). Even then, it is likely something will not build. Once you need C11/++11, everything breaks down, since gcc does not support building FAT binaries (driver-driver is needed).

Macports has a tool to make it work in principle (muniversal PGs), but a) it does not always reliably work even with Intel, b) cross-family builds are a pain, c) most of the ports do not use muniversal PG, which means they cannot be built as universal; you may try adding it locally, but you are likely to be on your own there.

You could build in Rosetta, however, for ppc (without universal). Just set the build_arch to ppc in macports.conf. I never tried that on 10.4–10.5, but it should work, I think. On 10.6.8 it does work, though you gonna need a few fixes from my branch.

I wish there was an easier way to:

1. Build for Intel, natively
2. Build for PPC, using Rosetta
3. Lipo everything together

As long as the port builds on both Intel and PPC (without universal), this should work, shouldn't it?

 

[barracuda156]

I wish there was an easier way to:

1. Build for Intel, natively
2. Build for PPC, using Rosetta
3. Lipo everything together

As long as the port builds on both Intel and PPC (without universal), this should work, shouldn't it?

I think this is what muniversal PortGroup does in effect. Perhaps, doing is manually will help to avoid quite a number of issues. I am not sure if it gonna be easier and/or faster though.

(But the real solution is to fix driver-driver in gcc.)

 

[pipetogrep]

If you still have the PowerMac from your signature (Dual 1.8 GHz Sonnet Encore), that should be decent to build from source natively. Huge stuff gonna take a while still, but otherwise it should not be a pain.
I have Dual 2.3, and it feels generally okay.

I do. gcc7 and libgcc7 are brutal, though.

 

[barracuda156]

I do. gcc7 and libgcc7 are brutal, though.

You just haven’t tried to build guile 3

For Rosetta, in principle you should be able to install 10.6 on MacMini 2012 (custom kernel needed, it is available publicly) and build for older SDK.
Setting up Macports to build only for ppc in Rosetta works fine. There are minor complications, but it is doable.
Still, multicore G5s gonna be faster, just give them a lot of RAM and SSD.