port select python and config error
Ryan Schmidt
ryandesign at macports.org
Sun Oct 28 22:46:23 UTC 2018
On Oct 28, 2018, at 16:50, Mark Brethen wrote:
> brethen-air:~ marbre$ port select --summary
> Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'.
> Name Selected Options
> ==== ======== =======
> clang none mp-clang-6.0 none
> cython none cython36 none
> gcc none mp-gcc7 none
> ipython py34-ipython none
> llvm none mp-llvm-3.4 mp-llvm-6.0 none
> mpi none mpich-mp-fortran none
> nosetests none nosetests36 none
> pip pip34 none
> py-sympy py36-sympy py36-sympy none
> python python27 python26-apple python27 python27-apple python36 none
> python2 python27 python26-apple python27 python27-apple none
> python3 python36 python36 none
> wxWidgets none wxWidgets-3.0 none
>
> With macports python 2.7 it’s a different error:
>
> :info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python: can't open file 'setup.py': [Errno 2] No such file or directory
> :info:build Command failed: cd "/opt/local/var/macports/build/_Users_marbre_ports_math_reduce/libreduce/work/Reduce-svn4765-src/generic/libreduce/x86_64-mac_10.12_sierra-darwin16.7.0" && /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg build
> :info:build Exit code: 2
> :error:build Failed to build libreduce: command execution failed
> :debug:build Error code: CHILDSTATUS 96796 2
> :debug:build Backtrace: command execution failed
> :debug:build while executing
> :debug:build "system {*}$notty {*}$nice $fullcmdstring"
> :debug:build invoked from within
> :debug:build "command_exec build"
> :debug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
> :debug:build "$procedure $targetname"
> :error:build See /opt/local/var/macports/logs/_Users_marbre_ports_math_reduce/libreduce/main.log for details.
>
> <main.log>
>
In that logfile, autoreconf has run, but configure has not been run, which is probably why the build later fails. I don't know why configure hasn't been run.
On Oct 28, 2018, at 17:03, Mark Brethen wrote:
> It looks to me that it failed because the source does not provide a ‘setup.py’ configuration file. Apple must provide a default setup.
setup.py is where a python project defines how it is to be set up. It's like a configure file. It's specific to each project. There isn't a default. Maybe for this software the configure script creates the setup.py file; I'm not sure.
More information about the macports-dev
mailing list