Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!lll-lcc!unisoft!hoptoad!rtech!llama!jas
From: jas@llama.rtech.UUCP (Jim Shankland)
Newsgroups: comp.unix.wizards
Subject: Re: multiple-machine executables for Suns?
Message-ID: <1114@rtech.UUCP>
Date: Wed, 5-Aug-87 13:36:12 EDT
Article-I.D.: rtech.1114
Posted: Wed Aug  5 13:36:12 1987
Date-Received: Sat, 8-Aug-87 10:02:46 EDT
References: <1853@megaron.arizona.edu> <12646@sol.hi.UUCP>
Sender: news@rtech.UUCP
Reply-To: jas@llama.UUCP (Jim Shankland)
Organization: Hellcats of the Relational Navy, Inc.
Lines: 11

In article <12646@sol.hi.UUCP> kurt@hc.dspo.gov (Kurt Zeilenga) writes:
>In article <1853@megaron.arizona.edu> whm@arizona.edu (Bill Mitchell) writes:
>>I find myself frequently inconvenienced by the incompatibilities between
>>different Sun binaries....  It'd be nice to have an executable that
>>contains both Sun-2 and Sun-3 versions of the same program.  If you run
>>it on a Sun-3, it fishes out the Sun-3 code
>>and if you run it on a Sun-2, it fishes out the Sun-2 code.

Something like Pyramid's conditional symbolic links, but
based on CPU type, would be another approach; that strikes me
as a little more appealing than having one gigantic a.out file.