Re: dyld: lazy symbol binding failed: Symbol not found: _dgemv_

[Ben Abbott]

On Jul 17, 2013, at 8:59 AM, CdeMills wrote:

> One more annoyance under Mac OS X.
> 
> I upgraded MacPorts last week, and since them I have occasionally Octave
> hanging with
> dyld: lazy symbol binding failed: Symbol not found: _dgemv_
>  Referenced from: /opt/local/lib/octave/3.6.4/liboctave.1.dylib
>  Expected in: /opt/local/lib/libarpack.2.dylib
> 
> Dyld: Symbol not found: _dgemv_
>  Referenced from: /opt/local/lib/octave/3.6.4/liboctave.1.dylib
>  Expected in: /opt/local/lib/libarpack.2.dylib
> 
> panic: Trace/BPT trap: 5 -- stopping myself...
> attempting to save variables to 'octave-core'...
> save to 'octave-core' complete
> 
> Process Inferior Octave trace/BPT trap: 5
> 
> The strange point is that, in /opt/local/lib:
> 
> grep _dgemv_ libarpack*
> Binary file libarpack.2.dylib matches
> Binary file libarpack.a matches
> Binary file libarpack.dylib matches
> 
> Did some other persons notice it under MacOS ? Should I report it on macport
> user list ?
> 
> Regards
> 
> Pascal

I haven't seen this, but the portfile for Octave-3.6.4 was recently updated (I 
worked with one of the macports maintainers on that).  One of the things that 
changed was that atlas became a default variant.   Are you using the atlas or 
accelerate variant?

Any chance you can provide a script that reproduces the problem?

Ben