The elf how-to briefly mentions something about this, it says:
"just compile all the object files with -fPIC, then link with a
command like
gcc -shared -Wl,-soname,libfoo.so.y -o libfoo.so.y.x *.o
If that looks complex, you obviously haven't ever read up on the
equivalent procedure for a.out shared libraries, which involves com-
piling the library twice, reserving space for all the data you think
that the library is likely to require in future, and registering that
address space with a third party (it's described in a document over 20
pages long --- look at
<ftp://tsx-11.mit.edu/pub/linux/packages/GCC/src/tools-2.17.tar.gz>
for details)."
I think that is what you want.
Ioannis Tambouras
[EMAIL PROTECTED], West Palm Beach, Florida
Signed pgp-key on key server.
On Fri, 28 Feb 1997, Dale Martin wrote:
> Hello,
>
> I have built a PCCTS source package - PCCTS is the "Purdue
> Compiler-Construction Tool Set" - it produces LL(K) parsers. I'm
> using it in a project which I will eventually Debianize. The PCCTS
> package is close to ready to upload, except it has some libraries in
> it, and I would like to compile them as shared libraries and don't
> know how. (I'd also like to use shared libraries in my own project.)
>
> Can anyone point me to an online reference on how to compile and use
> shared libraries? Note that I'm also interested in the portability of
> the solution - my project also is working with Linux/Alpha, and
> Solaris machines...
>
> Thanks for any info!
>
> Dale
>
>
