I think I understand now why octave is so
twitchy. The octave configure is not forcing the
use of -fPIC for the compilation of object code
going into shared libraries. I am in the process
of some test builds but the use of non-PIC code
can cause really obscure crashes to occur. We
also need to make sure that none of the shared
libraries created by octave link in static libs
directly. If so these must be created with
-fPIC as well.
Jack
ps If I recall correctly from my ppclinux days,
this non-PIC code in shared libraries can be
particularly buggy in the case of c++ code.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
