<GeDaMo>
"Rhapsody OS: Installing Apple’s Lost x86 OS from 1998 on a 3.4 Ghz i7 CPU & SSD"
<kof673>
some manpage IIRC: for malloc(0) we return a stupid answer to a stupid question
<nortti>
GeDaMo: that sounds interesting, I remember it being a bit cranky on anything newer than the original pentium
<GeDaMo>
Yeah, it seems to be a bit particular about hardware
<zid>
I mean, what isn't
<zid>
anything at all running on 20 year newer hw is a shitshow
<nortti>
I actually do have an install of it here, tho that's on the pentium 1 machine where I'd need to replace the RTC
<zid>
like, bringing up multi-socket systems with 2xapics and >4GB of ram etc with 'code that can bring up a pentium pro' is.. more luck than skill :P
<nortti>
should maybe see if I can swap the disk over to the other pentium machine, or if I'd need to reinstall
<kof673>
nextstep and openstep IIRC you had better luck with IDE disk either on same controller with cd-rom or ensuring they were separate, don't recall
<nortti>
I'm pretty sure I only have one IDE controller hooked up in there
<kof673>
i linked a long time ago someone was doing a frankenkernel from darwin, but don't think they were doing rhapsody :D
<nortti>
was that the darwin 0.3 stuffs, or something else?
<kof673>
probably, i can't imagine it went anywhere but lol
<kof673>
the problem with next is it wants apple cctools (binutils) and apple gcc etc. which assumes you have the next/apple headers/etc. so a cross-compiler is out generally IIRC
<kof673>
and people might have found fixes for linux -> mac os, but that is likely too new for next/openstep/rhapsody
<kof673>
*wants the headers to build your toolchain i mean IIRC
<kof673>
smallerc can target macos, maybe would be easier to get a cross toolchain with that
<kof673>
but that is just c of course, not obj c or c++
<nortti>
oh yeah I think I've seen someone get like python 3.10 running on rhapsody with that
gog has joined #osdev
gog has quit [Client Quit]
gog has joined #osdev
divine has quit [Ping timeout: 268 seconds]
<kof673>
that is more ridiculous: But if the committee says we're not fixing ISO C until the > > > > implementations are fixed, and the implementations (you) refuse to > > > > accept the fix until the committee standardizes something
<kof673>
if it is already out of bounds.....then its not a break to "fix" it. stand up for yourself ISO C!
<kof673>
breakage and Breakage ...breakage of documented behavior, versus breakage of things people weren't supposed to be relying on anyways (from ISO C POV anyways)
divine has joined #osdev
<kof673>
Rhapsody DR1 (Grail) it was actually code named grail, so when i joke about the tree of write once run everywhere, with openstep/java/.net, and everyone wants the portability grail, that works best there
goliath has joined #osdev
sprock has joined #osdev
netbsduser has quit [Remote host closed the connection]
netbsduser has joined #osdev
karenw has joined #osdev
sbalmos has quit [Quit: WeeChat 4.6.3]
corinne has quit [Remote host closed the connection]