Hi all, I there a chance that somebody would have a closer look at Ticket #35141 ?
This ticket seems to be around for a while already. However, py-scipy is an important dependency of a port I am trying to maintain (py-obspy) and I would like to keep python26 as well. From what I understand, the problem occurs only for py26-scipy and when build with gcc >= 4.5. For +gcc44 it works fine. I would not completely exclude the problem is actually somewhere (at least partly) in gcc or python 2.6, handling of symbol name or scipy making assumptions on symbol naming which are no more valid anymore. The somewhat strange thing is that for python 2.7 all works well for any gcc variant. I tested on two Mac OS X versions (10.5 and 10.8). I have probably not the capabilities to look into this in more detail, but I can help with testing/debugging. BTW: Is there a way to depend on a specific variant of a port? Or can someone point me to there right document/wiki/Howto? I have not found it. Is it a good idea for let's say py26-obspy default to py26-obspy +gcc44 (instead of py26-obspy +gcc47) and to require py26-scipy +gcc44 as dependency. Would it be a good idea to make py26-scipy +gcc44 the default for the moment? At least as a workaround until the ticket is fixed? Thanks a lot! ~petr
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
