home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.misc
- Path: sparky!uunet!charon.amdahl.com!amdahl!rtech!sgiblab!swrinde!gatech!paladin.american.edu!howland.reston.ans.net!bogus.sura.net!udel!princeton!nimaster.princeton.edu!cedman
- From: cedman@princeton.edu (Carl Edman)
- Subject: Re: How to convert BSD a.out files to Mach files using atom
- In-Reply-To: Charles William Swiger's message of Tue, 26 Jan 1993 23:52:40 -0500
- To: Charles William Swiger <infidel+@CMU.EDU>
- Message-ID: <CEDMAN.93Jan27081725@capitalist.princeton.edu>
- Originator: news@nimaster
- Sender: news@Princeton.EDU (USENET News System)
- Nntp-Posting-Host: capitalist.princeton.edu
- Organization: Princeton University
- References: <gfNVIM200WB3QHXHhM@andrew.cmu.edu>
- Date: Wed, 27 Jan 1993 12:17:25 GMT
- Lines: 22
-
- In article <gfNVIM200WB3QHXHhM@andrew.cmu.edu> Charles William Swiger <infidel+@CMU.EDU> writes:
- Atom converts executables and object files compiled for the NeXT in the
- BSD4.3 a.out format into the Mach-O format. There is no way that it is
- going to be able to convert an executable compiled for a different
- machine into something runable on the NeXT. (Why? Amoung many reasons,
- the Sun executable likely was compiled for a different *CPU* than the
- 680x0...)
-
- You will have to get the source code to whatever it is and recompile it
- for the program to run on your NeXT. (Sorry...)
-
- Not quite. Actually it has been done with Sun binaries, but all
- instances I remember have been two aeons (ie. operating system
- versions) or more ago. Of course the initial binary has to be a Sun-3
- binary (ie. 680x0 code) and it certainly has to be statically linked
- (aren't all Sun-3 binaries ?). Doubtlessly there also are plenty of
- programming constructs which break this, and possibly the black magic
- which is needed to make it work is gone from modern NeXT OS
- distributions. All I am saying is that it has been done.
-
- Carl Edman
-
-