#44310: py-pyepl @1.0.29: fails to build -----------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyepl | -----------------------+-------------------------------- Changes (by petr@…): * version: 2.3.1 => -- Ticket URL: <https://trac.macports.org/ticket/44310#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#44310: py-pyepl @1.0.29: fails to build -----------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-pyepl | -----------------------+-------------------------------- Comment (by petr@…): Okay, so I understood this wrong. I thought the port versions was intended for base related issues only, while port defect would usually affect various version so should not be specified. So I would leave the port version on which the defect was observed, right? -- Ticket URL: <https://trac.macports.org/ticket/44310#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#44310: py-pyepl @1.0.29: fails to build -----------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: py-pyepl | -----------------------+-------------------------------- Comment (by mf2k@…): Yes, definitely for port tickets, not just base tickets. -- Ticket URL: <https://trac.macports.org/ticket/44310#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#44310: py26-pyepl @1.0.29: fails to build -----------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: py-pyepl | -----------------------+-------------------------------- Comment (by petr@…): You are right! However, the port only offers `py26-pyepl` subport so there is no real ambiguity, and that's probably why I forgot this. The issue surfaced with r122244 and I wanted this to be documented. The port is unmaintained since years and probably the software upstream as well. So probably this just normal bit rot of an used port. I have not found any explicit hint that Python 2.7 is supported, but it might work. -- Ticket URL: <https://trac.macports.org/ticket/44310#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X

#44310: py26-pyepl @1.0.29: fails to build -----------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: py-pyepl | -----------------------+-------------------------------- Comment (by petr@…): The failure still occurs and the problem is basically the same. It is a C++ compilation issue. The unrecognized compiler flag is probably not relevant here. I attached the complete `main.log` for the python27 build. {{{ :debug:build Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.m acports.org_release_tarballs_ports_python_py- pyepl/py27-pyepl/work/pyepl-1.0.29" && /opt/local/Library/Framewor ks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg build :info:build g++ -fno-strict-aliasing -mno-fused-madd -fno-common -dynamic -DNDEBUG -O2 -Wall -I/opt/local/L ibrary/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c eplSound.cpp -o eplSound.o :info:build g++: warning: '-mfused-madd' is deprecated; use '-ffp- contract=' instead :info:build eplSound.cpp: In constructor 'eplSound::eplSound(long int, long int, int, int)': :info:build eplSound.cpp:27:10: error: 'EXIT_FAILURE' was not declared in this scope :info:build exit(EXIT_FAILURE); }}} The current version seems to be @2.3.1, now. So we just might want to update first. -- Ticket URL: <https://trac.macports.org/ticket/44310#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X

#44310: py-pyepl @1.0.29: fails to build -----------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: py-pyepl | -----------------------+-------------------------------- Comment (by larryv@…): Updating would be a good first step. The port also doesn’t [[UsingTheRightCompiler|use the right compiler]], so that should be addressed as well. -- Ticket URL: <https://trac.macports.org/ticket/44310#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X