Re: clues to statically building octave w/extensions?

[A. Danial]

On Fri, Jun 15, 2001 at 09:54:30AM -0500, Bill Lash wrote:
> > This is revealing information; when I issue
> >   find /usr/local/gcc/lib -name "lib*"
> > I see that every library file either ends with ".a" or "a.2.10.0".
> > There's not a single .so or .so.XX library!  This must explain
> > why the shared objects never load.  Time to go back and rebuild
> > gcc with a different setup (I think  configure  --enable-shared is
> > what gcc needs).    -- Al
> > 
> 
> Or maybe not.  I don't know how AIX names their shared libraries.  It
> very well coud be the a.2.10.0 is a shared library.  You might want to
> check this out first.  Would the "file" command tell you if it is a
> shared library?

AIX does use the .so extension to name shared objects.  I rebuilt
gcc (2.95.3) with --enable-shared during the configure step and behold! 
the gcc lib's now have .so and .so.2.10.0 extensions, and many .a lib's 
are symbolically linked to the .so's.  

So I rebuilt octave (2.1.34) with this new gcc fully expecting
dynamic loading and mkoctfile to work.  No such luck.  Same
ld errors as always.  

I have to decide how best to spend my time now:  pursuing this endless
quest to fix dynamic linking on AIX, or suffer the hassle of building
all my extensions statically.  I'm all out of ideas on the dynamic
link issue though.        -- Al



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------