DEFUN_DLD link rule

[Mike Miller]

Can someone comment on the necessity of explicitly linking in the
Octave libraries liboctinterp and liboctave when building oct-files?
Particularly with regard to non-GNU operating systems.

Oct-files are shared objects that are dlopen'd by Octave at runtime on
demand, while the Octave libraries have already been loaded by the
executable. In my experience, on GNU/Linux at least, it's not
necessary (and sometimes even discouraged) to link in libraries that
the application is expected to have already loaded.

What about other operating systems? If we were to remove
liboctinterp.la and liboctave.la from LIBADD, would this still work on
all other systems that we currently work on? And the same for the
mkoctfile command?

The reason I ask is because of a build problem on BSD, where libtool
is refusing to create shared libraries out of the dldfcn functions
because of a static system library in the dependency chain via
liboctave and liboctinterp. If I remove those libraries from the link
rule for all oct-files in dldfcn, they are linked correctly and all is
good again.

Thanks,

-- 
mike