Meanwhile, seeing what @marcan42 just did...
Having a Mach-O header present through a linker script for an _ELF_ linker is… let’s say quite unique.
This is a Linux bootloader, why would I force people to get a mach-o toolchain to compile it? That would be silly, when mach-o is just being used as a completely unnecessary wrapper format for what should have been a simple bare-metal binary blob. 
-
-
You must feed the Mach-O monster. We put plists in them after all! (OK, those have good reasons...)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We put mach-o's into mach-o's over here (see FAT binaries). Some day's I almost wonder how APFS format isn't a mach-o itself.
-
Sure, but the fat binary format has different magic and no load commands, it doesn't really have anything in common with what it is wrapping, we just call it a mach-o. Now MH_FILESET on the other hand…
- Show replies
New conversation -
-
-
Hmmm? There are very good reasons for it to be a Mach-O, mainly the thing that it’s the macOS kernel loading path. Are you advocating for kernelcaches to be flat files? And for compiling Mach-Os, you just need clang and lld installed on the system, shouldn’t be a big hurdle.
-
Linux ARM64 kernels are flat files even though Linux is an ELF system :-) clang "shouldn't be a big hurdle" but it's a bigger hurdle than the aarch64-linux-gnu-gcc that every person compiling anything on arm64 linux already has available.
- Show replies
New conversation -
-
-
I don't think this is the first time i've seen this kind of hack. Pretty sure some Linux distros used to build EFI apps by slapping a PE header on an ELF and embedding some code which processed ELF relocations
-
It’s the EFI stub code in the kernel indeed.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.