Opened 14 years ago

Closed 13 years ago

#21810 closed defect (fixed)

PyEPL building fail under SnowLeopard

Reported by: macports@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.1
Keywords: snowleopard Cc: jameskyle@…
Port: py26-pyepl

Description (last modified by jmroot (Joshua Root))

PyEPL suffers from two issues: Dependency on active wire, which is broken according to Ticket #21662.

But even if you manually exclude the dependency, you run into a building/activation error which is connected to a bad directory structure.

DebugLog attached.

Attachments (1)

py26-pyepl_debug.log (2.9 KB) - added by macports@… 14 years ago.
Excerpt from DebugLog for failed installation of py26-pyepl port.

Download all attachments as: .zip

Change History (8)

Changed 14 years ago by macports@…

Attachment: py26-pyepl_debug.log added

Excerpt from DebugLog for failed installation of py26-pyepl port.

comment:1 Changed 14 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to jameskyle@…

comment:2 Changed 14 years ago by jameskyle@…

Owner: changed from jameskyle@… to nomaintainer

After spending more than a few hours on this, it looks like a squarely upstream problem. As such, and in combination with this library no longer being used in my lab, I'm changing to nomaintainer. I'll stay on the cc list and if the original author updates the library for building on Snow Leopard I'll push the changes.

The problem is that the activewire library/module is deeply coupled with pyepl unless I'm missing something.

-james

comment:3 Changed 14 years ago by jameskyle@…

Cc: jameskyle@… added

Cc Me!

comment:4 Changed 13 years ago by jmroot (Joshua Root)

Keywords: pyepl removed
Owner: changed from nomaintainer to macports-tickets@…

comment:5 Changed 13 years ago by jmroot (Joshua Root)

Description: modified (diff)

comment:6 Changed 13 years ago by jmroot (Joshua Root)

The activewire dependency was removed in r59618. James, was this because it failed to build at the time, and can it be brought back now?

PyEPL's build system is broken in that it gives a 0 return code when it fails. So I imagine what happened is that it failed to build, but MacPorts thought it had succeeded, but it hadn't installed any files, so it then failed to activate.

comment:7 Changed 13 years ago by jmroot (Joshua Root)

Keywords: snowleopard added
Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.