On Tue, 10 Jan 2006, Martin Costabel wrote:
Viv Kendon wrote:
[]
error: `dispatch' undefined near line 2 column 1
error: near line 2 of file
`/sw/share/octave/2.1.71/site/m/octave-forge/comm//PKG_ADD'
error: source: error sourcing file
`/sw/share/octave/2.1.71/site/m/octave-forge/comm//PKG_ADD'
octave:1> b=rand(3,3)
error: `rand' undefined near line 1 column 3
error: evaluating assignment expression near line 1, column 2
Still struggling here...I think (not exhaustively tested)
everything in
/sw/lib/octave/2.1.71/oct/powerpc-apple-darwin
(including for example, rand, det, eig, fft, but not
including dispatch) fails to load properly in octave (with
or without octave-forge installed). The only thing I can
possibly find in common with all these during the build, is
warnings like this:
g++-3.3 -c -no-cpp-precomp -I/sw/include -I. -I..
-I../liboctave -I../src -I../l
ibcruft/misc -DHAVE_CONFIG_H -Wall -W -Wshadow -g -O2
./DLD-FUNCTIONS/eig.cc -
o eig.o
g++-3.3 -bundle -bundle_loader ../src/octave -L/sw/lib -o
eig.oct eig.o -L../lib
cruft -lcruft -L../liboctave -loctave -L. -loctinterp
-framework vecLib -lfftw3
-lreadline -lncurses -ldl -lhdf5 -lz -lm -L/sw/lib -lg2c
ld: warning multiple definitions of symbol _xerbla_
./liboctinterp.dylib(single module) definition of _xerbla_
../libcruft/libcruft.dylib(single module) definition of
_xerbla_
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fra
mework/Versions/A/libBLAS.dylib(single module) definition of
_xerbla_
Could someone confirm that these warnings are harmless
(especially the appearance of that system lib)?
In the octave mailing lists, similar "dispatch" errors occur
fairly often, and most of the replies seem to suggest things
are wrong with the build, but on linux the builds look so
different I haven't managed to gain any insight there yet.
They also suggest setting up .octaverc files to explicitly
control the load path, but this doesn't work for me, I think
it only works if the octave-forge stuff tries to load in the
wrong order. If, as in my case, there is something basic
wrong with octave itself then this isn't enough to fix it.
many thanks...
-- Viv
------------------------------------------------
Dr Viv Kendon [EMAIL PROTECTED]
Quantum Information tel: 0113 343 3858
Physics & Astronomy University of Leeds
http://quantum.leeds.ac.uk/~viv
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
