pauldmccarthy
commented
3 years ago I just noticed that my macOS environment ended up with octave 4.2.1, despite the latest available being 6.2.0 (which is the version that ended up being installed in my Linux environment). If I create the environment like so, omitting openmp:
conda create -c conda-forge -p ./test_octave_env octave make cxx-compilerThen I end up with the correct version - 6.2.0. However, in this environment, attempts to pkg install -forge io result in linking errors like:
ld: library not found for -lomp
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Makefile:6: num2col.oct] Error 1
make: *** Waiting for unfinished jobs.... which is why I was also installing openmp.
Attempts to create an environment with this command:
conda create -c conda-forge -p ./test_octave_env "octave==6.2.0" openmp make cxx-compilerresult in conflict errors:
Collecting package metadata (current_repodata.json): done
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: -
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
Package llvm-openmp conflicts for:
octave==6.2.0 -> fftw[version='>=3.3.9,<4.0a0'] -> llvm-openmp[version='>=10.0.1|>=11.0.0|>=4.0.1|>=8.0.0']
openmp -> llvm-openmp[version='8.0.0|8.0.0|8.0.1',build='h770b8ee_1|h770b8ee_0|h770b8ee_0']
cxx-compiler -> c-compiler==1.1.3=h35c211d_0 -> llvm-openmp
octave==6.2.0 -> llvm-openmp[version='>=11.0.1']
Package zlib conflicts for:
openmp -> clangdev[version='5.0.0|5.0.0.*'] -> zlib[version='>=1.2.11,<1.3.0a0']
octave==6.2.0 -> zlib[version='>=1.2.11,<1.3.0a0']
octave==6.2.0 -> glib -> zlib[version='1.2.*|1.2.11|1.2.8']
Package libcxx conflicts for:
cxx-compiler -> clangxx_osx-64=11 -> libcxx[version='>=11.0.1|>=11.1.0|>=8.0.0']
cxx-compiler -> libcxx[version='>=10.0.0|>=10.0.1|>=11.0.0|>=9.0.1|>=9.0.0|>=8.0.1|>=4.0.1']
Note that strict channel priority may have removed packages required for satisfiability. 
izahn
enolfc
ngam
Issue:
Howdy, I am having trouble installing Octave packages using
pkg installwithin a conda-forge-installed version of Octave on macOS, for Octave packages which require compilation. Note that I am only seeing this error on macOS. On Linux, I am successfully able to install Octave, and usepkg install.The issue can be reproduced from a fresh miniconda install:
Then, within the octave session, running
pkg install -forge ioresults in the following trace:The
lderrors (snippet below) suggest that octave is constructing linker flags using paths that were hard-coded at the time that Octave was compiled.I'm not particularly experienced with Octave, so am unsure if this can be avoided via some sort of configuration option, or if the conda-forge-compiled Octave package needs to be patched.
Thanks!
Environment (
conda list):Details about
condaand system (conda info):