[MacPorts] #43092: port install octave +atlas+docs processing failed
#43092: port install octave +atlas+docs processing failed -------------------------+-------------------------------- Reporter: gbacareza@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: | Port: -------------------------+-------------------------------- Just installed Macports with the intention of using it to install Octave. Obviously I'm very new as I'm a first timer. When attempting to install Octave with command: sudo port install octave +atlas+docs, I get the Error: Processing of port octave failed. Questions: 1. Does this mean that Octave was not installed at all? 1a. Or does it mean that only the failed dependencies, (eg Error: The following dependencies were not installed: SuiteSparse atlas arpack gcc48 cctools ... ) were not installed? 1b. If on the contrary Octave was installed except for dependencies, where could I find executable? 2. What happened to all the dependencies that were installed eg Installing libxml2 @2.9.1_0 which had no errors? 2a. Where were they installed? 3. What do terms "Activating" and "Cleaning" (eg ---> Installing libtool @2.4.2_3 ---> Activating libtool @2.4.2_3) actually do? 3a. Do they overwrite libraries and files already there before this operation? 4. If I decide to not attempt the port installation of Octave and try other means, how do I clean up? -- Ticket URL: <https://trac.macports.org/ticket/43092> MacPorts <http://www.macports.org/> Ports system for OS X
#43092: port install octave +atlas+docs processing failed --------------------------+-------------------------------- Reporter: gbacareza@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by ryandesign@…): The issue tracker is for reporting problems. It appears that on your system, octave could not be installed, because one of its dependencies failed to install. That's a problem, and you should attach the main.log file of the port that failed to install. (You attached the log for octave, which tells us nothing.) As to the rest of your questions, they're best asked and answered on the macports-users mailing list. -- Ticket URL: <https://trac.macports.org/ticket/43092#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#43092: port install octave +atlas+docs processing failed --------------------------+-------------------------------- Reporter: gbacareza@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by gbacareza@…): attached correct file -- Ticket URL: <https://trac.macports.org/ticket/43092#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#43092: atlas: Atlas could not detect any fortran compiler --------------------------+--------------------- Reporter: gbacareza@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => vince@… * port: => atlas Comment: The log is fairly straightforward; the error message it contains describes what you have to do:
Atlas could not detect any fortran compiler. If you really don’t need the fortran interface to be built, please use the +nofortran option, else install a fortran compiler (e.g. gcc4X) before building Atlas.
-- Ticket URL: <https://trac.macports.org/ticket/43092#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#43092: atlas: Atlas could not detect any fortran compiler --------------------------+--------------------- Reporter: gbacareza@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Comment (by jad11@…): Replying to [comment:3 ryandesign@…]:
The log is fairly straightforward; the error message it contains describes what you have to do:
Atlas could not detect any fortran compiler. If you really don’t need the fortran interface to be built, please use the +nofortran option, else install a fortran compiler (e.g. gcc4X) before building Atlas.
At risk of hijacking the ticket, but in the hope that my experiences will assist in solving the problem, I wanted to report that I am also having similar problems with the atlas install. Having read your advice, I have made several further attempts with and without gcc48 but without success. In my most recent attempt, I started from a brand new macports installation, and performed just: {{{ sudo port selfupdate sudo port upgrade outdated sudo port install gcc48 sudo port install atlas +gcc48 }}} The terminal output for the final command is: {{{ jad11:~$ sudo port install atlas +gcc48 Password: ---> Computing dependencies for atlas ---> Fetching archive for atlas ---> Attempting to fetch atlas-3.10.1_5+gcc48.darwin_13.x86_64.tbz2 from http://packages.macports.org/atlas ---> Attempting to fetch atlas-3.10.1_5+gcc48.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/atlas ---> Attempting to fetch atlas-3.10.1_5+gcc48.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/atlas ---> Fetching distfiles for atlas ---> Attempting to fetch atlas3.10.1.tar.bz2 from http://aarnet.dl.sourceforge.net/project/math-atlas/Stable/3.10.1 ---> Attempting to fetch lapack-3.4.2.tgz from http://www.netlib.org/lapack ---> Verifying checksums for atlas ---> Extracting atlas ---> Applying patches to atlas ---> Configuring atlas Selected C compiler: /opt/local/bin/gcc-mp-4.8 Selected F77 compiler: gfortran48 Warning: GCC compilers on MacOS do not support AVX: downgrading. Error: org.macports.configure for port atlas returned: configure failure: command execution failed Please see the log file for port atlas for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port atlas failed }}} The pertinent section from the atlas install log would appear to be: {{{ :info:configure /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build/..//CONFIG/include/atlconf.h:4:19: fatal error: stdio.h: No such file or directory :info:configure #include <stdio.h> :info:configure ^ :info:configure compilation terminated. :info:configure make: *** [atlconf_misc.o] Error 1 :info:configure ./xconfig -d s /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build/../ -d b /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build -Si lapackref 1 -O 12 -v 5 -D c -DATL_DYLIBS -A 26 -V 448 -Si omp 0 -C acg /opt/local/bin/gcc-mp-4.8 -A 25 -F acg '-fomit-frame-pointer -mfpmath=sse -O3 -fno-schedule-insns2 -fPIC -msse4.2' -C if /opt/local/bin/gfortran- mp-4.8 -F if '-fomit-frame-pointer -mfpmath=sse -O3 -fno-schedule-insns2 -fPIC -msse4.2' -Ss f77lib /opt/local/lib/gcc48/libgfortran.dylib -b 64 -D c -DPentiumCPS=2800 :info:configure /bin/sh: line 1: ./xconfig: No such file or directory :info:configure xconfig exited with 127 :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/build" && ../configure --prefix=/opt/local --with-netlib-lapack- tarfile=/opt/local/var/macports/distfiles/atlas/lapack-3.4.2.tgz -O 12 -v 5 --dylibs -A 26 -V 448 -Si omp 0 -C acg /opt/local/bin/gcc-mp-4.8 -A 25 -F acg '-fomit-frame-pointer -mfpmath=sse -O3 -fno-schedule-insns2 -fPIC -msse4.2' -C if /opt/local/bin/gfortran-mp-4.8 -F if '-fomit-frame-pointer -mfpmath=sse -O3 -fno-schedule-insns2 -fPIC -msse4.2' -Ss f77lib /opt/local/lib/gcc48/libgfortran.dylib -b 64 -D c -DPentiumCPS=2800 :info:configure Exit code: 127 :error:configure org.macports.configure for port atlas returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "$procedure $targetname" :info:configure Warning: targets not executed for atlas: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port atlas for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/main.log }}} Thanks for your help Andy -- Ticket URL: <https://trac.macports.org/ticket/43092#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#43092: atlas: Atlas could not detect any fortran compiler --------------------------+--------------------- Reporter: gbacareza@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: atlas | --------------------------+--------------------- Comment (by vince@…): Sorry to chime in a bit lately. This last error is caused by a problem in the Xcode installation. The Fortran compiler is detected all right, but something is wrong with the C compiler. It's not the first time this happens. I am a bit swamped lately, so I have little time, but if you do a quick scan through the tickets archives and look for Atlas, you'll 100% sure find a similar case. -- Ticket URL: <https://trac.macports.org/ticket/43092#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts