On 14-Jul-2009, Christophe Tournery wrote:
| Could it be an issue with my build from MacPorts then? (Mac OS X
| 10.5.7, macports 1.710)
| I see that the Portfile configures octave with:
|
| configure.args --enable-shared \
| --enable-dl \
| --disable-static \
| --with-hdf5 \
| --with-fftw \
| --with-blas="-framework Accelerate" \
| --enable-static \
| --enable-readline \
| --with-zlib \
| --with-glpk \
| --with-curl \
| --with-lapack \
| --with-umfpack \
| --with-colamd \
| --with-ccolamd \
| --with-cholmod \
| --with-cxsparse
I have no idea. I don't have an OS X system, so I can't try to
reproduce the problem there. Maybe someone else can.
Can you run Octave under gdb and set a breakpoint in the function
octave_dynamic_loader::do_load_oct and see where/why the .oct file is
loaded multiple times? Looking at what happens in the function
octave_dyld_shlib::open might also give you some clues.
Also, can you try to use a PKG_ADD file with the lines
autoload ("mylib_init", "mylib.oct");
autoload ("mylib_desstroy", "mylib.oct");
autoload ("mylib_process", "mylib.oct");
instead of using symbolic links? Does that change anything?
Are the timestamps on your .oct files somehow in the future?
jwe
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
