Related articles |
---|
[3 earlier articles] |
Re: incremental compilation via shared library pardo@cs.washington.edu (1993-09-02) |
Re: incremental compilation via shared library assmann@prosun.first.gmd.de (1993-09-03) |
Re: incremental compilation via shared library brett@digits.enet.dec.com (1993-09-07) |
Re: incremental compilation via shared library pop@dcs.gla.ac.uk (pop) (1993-09-07) |
Re: incremental compilation via shared library pcg@decb.aber.ac.uk (1993-09-11) |
Re: incremental compilation via shared library tmb@arolla.idiap.ch (1993-09-20) |
Re: incremental compilation via shared library brent@jade.ssd.csd.harris.com (1993-09-20) |
Re: incremental compilation via shared library pcg@aber.ac.uk (1993-09-21) |
Re: incremental compilation via shared library jeremy@suite.sw.oz.au (1993-09-22) |
Re: incremental compilation via shared library gym@dcs.ed.ac.uk (Graham Matthews) (1993-09-22) |
Newsgroups: | comp.compilers |
From: | brent@jade.ssd.csd.harris.com (Brent Benson) |
Keywords: | linker |
Organization: | Compilers Central |
References: | 93-08-104 93-09-014 |
Date: | Mon, 20 Sep 1993 13:06:57 GMT |
# ... I think the biggest obstacle
# to incremental compilation in traditional environments (C/C++) is a
# dynamic object file loader.
#
# Well, you can hack one on most any BSD style environment -- indeed the
# '-A' option to 'ld' and successive equivalent variants was introduced
# to support extending Franz Lisp. SVR4 of course has a built-in dynamic
# object file loader.
I'm disappointed with the dynamic object file loader available in our
SVR4 port. dlopen() will load a shared object file and resolve
references to symbols in the original executable, but it will not
resolve references to symbols in other shared objects that were loaded
at run-time. Is this typical of SVR4 ports? What is the reason for
this restriction?
Brent Benson
Harris Computer Systems
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.