Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!jfc
From: jfc@athena.mit.edu (John F Carr)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: Dynamic Linking (was: Re: shared memory under AOS4.3??)
Message-ID: <1990Sep3.214519.23308@athena.mit.edu>
Date: 3 Sep 90 21:45:19 GMT
References: <1990Aug28.012633.28332@odin.corp.sgi.com> <1990Aug29.172240@ibmpa.awdpa.ibm.com> <1028@lee.SEAS.UCLA.EDU>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: Massachusetts Institute of Technology
Lines: 20

In article <1028@lee.SEAS.UCLA.EDU> jsin@seashell.seas.ucla.edu (Just Another John) writes:
>
>Well, speaking of shared memory, I was wondering if it is possible to link
>.o files at run time?  I'm porting a program written for SunOS which uses
>dynamic link-loading - I've read their code and attempted to modify it for 
>use on our Dec/88 AOS 4.3 RTs, but I haven't quite got it working
>(segmentation fault when trying to jump to the new routine).

The Andrew software package from CMU comes with a dynamic object loader.  If
you've got a spare few hundred megabytes of disk you could get that (or find
a source tree to copy the dynamic loader from).

I'm looking into real shared libraries (the right solution -- dynamic object
loading makes a copy of the .o file per process; a shared library only needs
to copy the modifiable data per process [which is probably only about 10-25%
of the text size]).


--
    --John Carr (jfc@athena.mit.edu)