There are many reasons that a parallel process canįail during opal_init some of which are due to configuration orĮnvironment problems. It looks like opal_init failed for some reason your parallel process is mca: base: component_find: unable to open /opt/openmpi/lib/openmpi/mca_carto_file: file not found (ignored) mca: base: component_find: unable to open /opt/openmpi/lib/openmpi/mca_carto_auto_detect: file not found (ignored) mca: base: component_find: unable to open /opt/openmpi/lib/openmpi/mca_paffinity_test: file not found (ignored) mca: base: component_find: unable to open /opt/openmpi/lib/openmpi/mca_paffinity_darwin: file not found (ignored) Problem when mpic++ points to the binary of a different Open MPI installation (in /usr/local/bin) instead of the new Open MPI installation (/opt/openmpi/bin): To shift the entire openmpi tree to another folder, add the following to ~/.bash_profile :ġ. Ld warning: in /opt/openmpi/lib/libopen-pal.dylib, file is not of required architecture Ld warning: in /opt/openmpi/lib/libopen-rte.dylib, file is not of required architecture Ld warning: in /opt/openmpi/lib/libmpi.dylib, file is not of required architecture Ld warning: in /opt/openmpi/lib/libmpi_f77.dylib, file is not of required architecture Ld warning: in /opt/openmpi/lib/libmpi_f90.a, file is not of required architecture Note that in future compiles, you'll need to specify '-m64', otherwise you'll get errors like: configure -prefix=/opt/openmpi163 CC=gcc CXX=g++ F77=gfortran FC=gfortran CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 2>&1 | tee config.out To produce 64 bit C,C++,F77, & F90 objects ( for the GNU compiler suite) : configure -prefix=/opt/openmpi163 CC=gcc CXX=g++ F77=gfortran FC=gfortran 2>&1 | tee config.out #for GNU Compilers configure -prefix=/opt/openmpi163 CC=icc CXX=icpc F77=ifort FC=ifort 2>&1 | tee config.out #for Intel Compilers If you need to specify the compiler bindings, you'll need to change the. Run your code using any of the following three options: To only just check the compilers, type: ompi_info | grep compilerĨ. Be patient.Which mpirun which mpiexec which ompi_info If you installed Octave as described in Install Octave on Mac OS X El Capitan you can (but you do not have to) change the graphics toolkit from Gnuplot to QT by simply delete or out-comment the following lines in your ~/.octaverc: #setenv("GNUTERM","wxt") In Octave 3.8.2 it was not possible to plot with FLTK. But please be patient it can take a while.īut its worth waiting because you get a new GNU Octave 4.0.3 on your drive. Than install GNU Octave with the right variants and get rid of the wrong ones: sudo port install octave -gcc5+gfortran-accelerate+atlas+docs+fltk+graphicsmagick+java-gui-metis-qtgui+app+qt4gui+soundĪfter that the installation succeeded. The labeled variants are installed by default. You see that the following variants are not supported anymore: Universal: Build for multiple architectures Sound: enable audio support (file I/O and playback) Openblas: Build with linear algebra from OpenBLAS Graphicsmagick: use GraphicsMagick for image I/O Gfortran: Build using the MacPorts gcc 5 Fortran compiler But this version has to be installed with other variants.Ĭhecking my old status via port installed | grep -i "octave" gave the following result: octave lookup the current variants I did port variants octave: octave has the variants:Īccelerate: Build with linear algebra from built-in Accelerate frameworkĪpp: build application bundle to launch octaveĪtlas: Build with linear algebra from ATLASĬlang37: Build using the MacPorts clang 3.7 compilerĬlang38: Build using the MacPorts clang 3.8 compilerĬlang39: Build using the MacPorts clang 3.9 compilerįltk: enable fltk as a graphics toolkit for plotting Currently MacPorts supports Octave 4.0.3 instead of 3.8.2 before. I installed GNU Octave via Install Octave on Mac OS X El Capitan. Unfortunately the update/grade of GNU Octave fails: Error: for port octave returned: must set at least one Fortran variant (e.g. To keep MacPorts and its ports up to date a frequently performed sudo port selfupgrade and sudo port upgrade outdated do the job.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |