Hi,

I had octave-atlas running successfully on three G4 Macs for 3 weeks 
now, so I thought it's time for a fink selfupdate and fink update-all.

When the process was finished this morning, octave was no longer working 
on 2 of the Macs. All are set to update directly from CVS. In the few 
minutes that I had to look at the problem, I noticed two things that may 
be clues to the error. This is not easy for me to see through because 
octave DOES work on one of my machines!

a) the broken octave exits with the message
dyld: octave Undefined symbols:
octave undefined reference to ___udivdi3 expected to be defined in 
/sw/lib/libhdf5.0.dylib
octave undefined reference to ___umoddi3 expected to be defined in 
/sw/lib/libhdf5.0.dylib

If I remember correctly, the HDF support is something that was added new 
in octave.

b) I tried to compile some of my own programs against libatlas.a in a 
way I had done successfully before. The compilation failed with the 
message that I should run ranlib on libatlas.a - and after that the 
compilation worked. This same compilation worked right away on the 
machine where octave works, but ALSO on one if the machines where octave 
didn't work ! Isn't that weird ?
So something must have gone wrong in the ATLAS installation on one of 
the Macs. Most of the installation log has been scrolled off my terminal 
buffer, because the 'update-all' ran for a couple of hours after I left 
for the night. Before leaving, I did see that ATLAS appeared to be 
working already because various automatic test programs were running 
(giving performance values above 1 GFlop on my dual-G4 Mac). So I'm 
really shocked this morning that precisely this dual-G4 doesn't run 
octave anymore.

I guess this is mainly a question for Jeffrey, but any help is welcome. 
And perhaps for now I would NOT recommend doing updates of octave if 
your installation is working fine !

Jens



_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to