Opened 10 years ago

Last modified 9 years ago

#44310 new defect

py-pyepl @1.0.29: fails to build

Reported by: petrrr Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.1
Keywords: Cc: Ionic (Mihai Moldovan), kurthindenburg (Kurt Hindenburg)
Port: py-pyepl

Description (last modified by petrrr)

The port fails to build on 10.8.5, it is unmaintained, main.log attached.

Update: This ticket was compiled for py26, but applies to py27 as well.

Attachments (2)

py-pyepl.main.log (122.1 KB) - added by petrrr 10 years ago.
py27-pyepl.main.log (129.5 KB) - added by petrrr 10 years ago.
A python27 build

Download all attachments as: .zip

Change History (15)

Changed 10 years ago by petrrr

Attachment: py-pyepl.main.log added

comment:1 Changed 10 years ago by petrrr

Version: 2.3.1

comment:2 in reply to:  1 Changed 10 years ago by mf2k (Frank Schima)

It is generally a good idea to indicate what version of port you used in any defect ticket because it can be very important in determining the issue.

comment:3 Changed 10 years ago by petrrr

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?

comment:4 Changed 10 years ago by petrrr

Version: 2.3.1

comment:5 Changed 10 years ago by mf2k (Frank Schima)

Yes, definitely for port tickets, not just base tickets.

comment:6 Changed 10 years ago by kurthindenburg (Kurt Hindenburg)

Cc: khindenburg@… added

Cc Me!

comment:7 Changed 10 years ago by kurthindenburg (Kurt Hindenburg)

Summary: py-pyepl @1.0.29: fails to buildpy26-pyepl @1.0.29: fails to build

you should include what version you are trying to install as well - I believe python27 is the default now

comment:8 Changed 10 years ago by petrrr

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.

comment:9 Changed 10 years ago by larryv (Lawrence Velázquez)

I created a subport for Python 2.7 but did not test it. The Python 2.6 one has been replaced.

Do you still see the failure with py27-pyepl?

Changed 10 years ago by petrrr

Attachment: py27-pyepl.main.log added

A python27 build

comment:10 Changed 10 years ago by petrrr

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.

comment:11 Changed 10 years ago by petrrr

Description: modified (diff)
Summary: py26-pyepl @1.0.29: fails to buildpy-pyepl @1.0.29: fails to build

comment:12 in reply to:  10 Changed 10 years ago by larryv (Lawrence Velázquez)

Updating would be a good first step. The port also doesn’t use the right compiler, so that should be addressed as well.

comment:13 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)

I think the livecheck url is wrong

-    livecheck.url   http://git.debian.org/?p=pkg-exppsy/pymvpa.git
+    livecheck.url   http://anonscm.debian.org/cgit/pkg-exppsy/pyepl.git

That shows the current version is 1.1.0 from 6 years ago

Note: See TracTickets for help on using tickets.