Yes, you can do this. You'd need to replace the compiler and then
build all projects, which I've provided instructions for on the
email@hidden mailing list.
However, Martin, why do you assume an OpenDarwin release will
change the hardware requirements in such a significant way? Every
deviation has maintenance requirements, and lowering the SSE2
requirements would make us even further binary incompatible with
Mac OS X for Intel.
Even if the OpenDarwin binary installer doesn't support more CPUs, it
would still be easier to build a replacement userland from OpenDarwin
source tree than from an Apple-Darwin release (just because the
latter often depends on closed APIs and needs to be patched, and the
patches probably came from a corresponding OpenDarwin release in the
first place!).
I don't understand what you mean about binary incompatibility
though. Let's say that OpenDarwin 8.2.1 is available with no SSE2
dependency, and Darwin 8.2.0 is the corresponding Darwin from OS X
10.4.2u with its SSE dependence. While it is true that libraries and
executables from 8.2.0 would not run everywhere an 8.2.1 system can
be found, the files wouldn't be binary incompatible would they? And
presumably executables and libraries from 8.2.1 would still run on
any 8.2.0 system, so anything is interchangable on any system *which
is supported* by both Darwin flavours, problems only occur if you are
using a system supported by one or the other *only*. If that's not
the case, I don't understand why but am willing to be told [what I
know about Mach-O - or any other binary format for that matter - can
be written across a motherboard track :-)]
Graham.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-x86 mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
