octave @4.2.2: dyld: Library not loaded: /opt/local/lib/libomp/libomp.dylib

[ryandesign (Ryan Carsten Schmidt)]

octave fails to activate on at least the ​10.6-x86_64 buildbot worker:

DEBUG: Executing proc-post-org.macports.activate-activate-0
DEBUG: system: /opt/local/bin/octave-cli -q -f -H --eval 'try; pkg prefix /opt/local/share/octave/packages /opt/local/lib/octave/packages; pkg -verbose -global rebuild; disp(lasterror.message); catch; exit(1); end_try_catch;'
dyld: Library not loaded: /opt/local/lib/libomp/libomp.dylib
  Referenced from: /opt/local/bin/octave-cli
  Reason: image not found
Command failed: /opt/local/bin/octave-cli -q -f -H --eval 'try; pkg prefix /opt/local/share/octave/packages /opt/local/lib/octave/packages; pkg -verbose -global rebuild; disp(lasterror.message); catch; exit(1); end_try_catch;'
Killed by signal: 5
Error: Failed to activate octave: command execution failed
DEBUG: Error code: NONE
DEBUG: Backtrace: command execution failed
    while executing
"$post $targetname"
Error: See /opt/local/var/macports/logs/_opt_bblocal_var_buildworker_ports_build_ports_math_octave/octave/main.log for details.

/opt/local/bin/octave-cli is apparently linked with /opt/local/lib/libomp/libomp.dylib, but the octave port doesn't declare a dependency on the libomp port.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

The latest Octave seems to exist in the ​packages server.
Can this ticket be closed?

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

I am not sure when, but this problem no longer seems to exist.