Opened 10 years ago

Last modified 8 years ago

#41541 new defect

py33-logilab-common installation failure

Reported by: RivetBenoit (Benoit Rivet) Owned by: stromnov (Andrey Stromnov)
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: petrrr
Port: py-logilab-common

Description

As explained in the title : on a Mac OS X.5 PPC machine, py33-logilab-common fails to build. Lines 373 and 374 of the main.log file read :

:info:build running 2to3 on build/lib/logilab/common/test/data
:info:build error: No such file or directory: '2to3'

The command ls /opt/local/bin/2* gives :

/opt/local/bin/2to3-2.7
/opt/local/bin/2to3-3.3

The command locate 2to3 gives a bunch of results, including :

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/2to3
/opt/local/Library/Frameworks/Python.framework/Versions/3.3/bin/2to3

Any workaround ?

For further detail : starting from line 373, the log file reads :

:info:build running 2to3 on build/lib/logilab/common/test/data
:info:build error: No such file or directory: '2to3'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-logilab-common/py33-logilab-common/work/logilab-common-0.60.0" && /opt/local/Library/Frameworks/Python.framework/Versions/3.3/bin/python3.3 setup.py --no-user-cfg build 
:info:build Exit code: 1
:error:build org.macports.build for port py33-logilab-common returned: command execution failed
:debug:build Error code: CHILDSTATUS 68495 1
:debug:build Backtrace: command execution failed
    while executing
"system -nice 0 $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: targets not executed for py33-logilab-common: org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Please see the log file for port py33-logilab-common for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-logilab-common/py33-logilab-common/main.log

Change History (6)

comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: stromnov@… added
Owner: changed from macports-tickets@… to dh@…

comment:2 Changed 10 years ago by RivetBenoit (Benoit Rivet)

Quick fix : py33-logilab-common compiles fine after choosing python33 as the default python environment, via :

sudo port select --set python python33

It should be useful to indicate that setting the default python in MacPorts should be required before installing py33-logilab-common (and any port depending on py33-logilab-common).

I was installing from scratch py33-spyder-devel (which meant quite a lot of ports to install), and the installation went smoothly except for some dependencies : iirc, py33-logilab-common depends on bison; which was listed as one of the many ports to install but which wasn't installed before py33-logilab-common. Installing manually the required dependencies (as found when reading the main.log file) before trying again to install py33-spyder-devel seemed a good fix... But in the end, I still could not install py33-spyder-devel, since it required three ports:

py33-pylint, py33-astroid and py33-logilab-common

who depend upon py33-logilab-common; and who won't build until python33 is set as the default python on the system. Before that, which python gave :

/usr/bin/python

i.e python 2.5.1 as installed on Mac OS X.5 PPC.

comment:3 Changed 10 years ago by RivetBenoit (Benoit Rivet)

Addendum : after fixing my problem, I finished installing py33-spyder-devel which now runs fine in Mac OS X.5 PPC. Thanks for the good work to all the people involved :-)

comment:4 Changed 9 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:5 Changed 8 years ago by petrrr

This ticket is now quite old, so it might have become irrelevant.

However, the described behavior looks like a bug. Ports should work without and default settings involved. Some call of a python interpreter would need to be replaced.

comment:6 Changed 8 years ago by mf2k (Frank Schima)

Cc: stromnov@… removed
Owner: changed from dh@… to stromnov@…
Port: py-logilab-common added; py33-logilab-common removed

dh has retired. See #51239.

Note: See TracTickets for help on using tickets.