
This is the README for the condor_compile command.


After installing condor_compile, you can compile for condor by typing :

  condor_compile <whatever you normally type to create an executeable>

For instance, if you normally compile by typing "f77 +e +O3 myprog.f",
typing "condor_compile f77 +e +O3 myprog.f" will result in a
condor executeable called a.out.condor.  (condor_compile will append
a ".condor" to whatever your executeable name normally comes out as).
You can type "condor_compile make myprogram", or "condor_compile
cc .....", whatever.  condor_compile currently works on HPUX and
on SunOS 4.1.x.  The whole idea behind condor_compile is a somewhat
ugly hack, but condor end-users who just want to use Condor without
a lecture on linking love it, and nothing else appears affected.

To Install:

1) Become root
2) move /bin/ld to /bin/ld.real :
     mv /bin/ld /bin/ld.real
3) edit the ld shell script located in the directory.  what you
   need to change is up at the top: change the values for
   CONDOR_CLIB and CONDOR_RT0 so that the path is correct for
   your local installation.
4) copy the ld shell script in this directory into /bin/ld:
     cp ./ld /bin/ld
     chown root /bin/ld
     chmod 555 /bin/ld
5) place the condor_compile shell script someplace in the condor 
   user's path:
     cp ./condor_compile /usr/local/condor/bin/condor_compile
     chmod 555 /usr/local/condor/bin/condor_compile

That's it.

The change should be transparent to non-condor users; i.e. the
condor_compile version of ld simply calls ld.real with all the
same command line parameters if not invoked from condor_compile.
We have condor_compile installed just about everywhere, and nobody
has complained (yet?).
The shell scripts are short and self-explanatory.

Enjoy.

Todd Tannenbaum
Nov 1993
UW-Madison CAE Model Advanced Facility

