Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!oz.cis.ohio-state.edu!jgreely From: jgreely@oz.cis.ohio-state.edu (J Greely) Newsgroups: comp.sys.next Subject: Re: Porting binaries Message-ID: Date: 29 Jul 89 14:29:07 GMT References: Sender: news@tut.cis.ohio-state.edu Reply-To: J Greely Distribution: usa Organization: Ohio State University Computer and Information Science Lines: 23 In-reply-to: mccalpin@masig2.ocean.fsu.edu's message of 28 Jul 89 18:36:12 GMT In article mccalpin@masig2.ocean.fsu.edu (John D. McCalpin) writes: >I have heard that it is possible to run sun3 binaries on the NeXT >(at least under 0.9). Since this one keeps coming up, I'll trash it publicly. The ability to run Sun 3 binaries was a feature of Mach that was supported under 0.8. It went bye-bye in 0.9. Having been removed, the chances of it reappearing are slim to none (leaning towards none, I'm sure). Personally, I was rather fond of it, since it drastically cut the time needed to make a NeXT look like the other workstations here. Since you can't just compile most software (usually, it's: compile, hack Makefile, compile, hack source, compile, hack includes, compile, hack Makefile...), you spend a *lot* of time localizing the machine. If we had 200+ NeXTs and 2 Suns, it wouldn't be a big deal, but it's the other way around... "And say a prayer, if you remember any. What the hell. Even now, a little flattery couldn't hurt." -=- J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)