Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ncoast.org!allbery
From: allbery@ncoast.org (Brandon S. Allbery)
Newsgroups: gnu.emacs
Subject: shared source question
Message-ID: <8906070311.AA13940@NCoast.ORG>
Date: 7 Jun 89 03:11:52 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 29

In your message of Sun, 04 Jun 89 18:13:48 PDT, you write:
+---------------
|     My question is this, is it possible (or even a good thing?) to use *one*
|     NFS mountable copy of the source tree (for any given version of emacs)
|     and a master Makefile to generate all the needed executables, thereby
|     saving 40+ meg of disc for each combination?
| 
| I maintain GNU Emacs for eight different machine types here: Apollo
| 68020/68030, Apollo PRISM, sun3, sun4, sun386, sun2, vax-ultrix, and
| vax-4.3bsd.  On the Apollo's, I can build a single compound executable (cmpexe)
| that can be run on both the 68020/68030 and PRISM based nodes, so users don't
| need to know what type of node they're using, and a single Emacs tree can
| be shared very easily.
| 
| Unfortunately, the Suns and Vaxes do not support a notion of compound
| executables, so more work is required to share a common Emacs tree, but it is
| possible and I've been running such a system here for a couple of months
| without any problems.
+---------------

Dumb question:  could Gnu /bin/ld be made capable of creating compound
executables of some kind?  (Not that I have seen the source to know the
reality of the situation, but could encapsulated COFF files be a model of
some kind for this?)

If I'm barking up the wrong tree, spare the lists and send me email; I'll go
away quietly.

++Brandon