Alexander Hansen <[email protected]> said: > I'll take bmaret off this thread, since we're now fighting with > python25, and cc _that_ maintainer. > > On Feb 28, 2009, at 8:53 PM, zooloo wrote: >> On Sat, 28 Feb 2009 22:51:36 +0100, Martin Costabel <[email protected] >> > wrote: >> >>> What you need to find out is why your python25 decides not to build >>> the _sha* modules. There is some logic in setup.py that looks at >>> openssl versions and then decides to build _sha256.so. >> >> Here are the version info you requested: >> >> $ /usr/bin/openssl version >> OpenSSL 0.9.7l 28 Sep 2006 >> >> $ grep VERSION_NUMBER /usr/include/openssl/opensslv.h >> #define OPENSSL_VERSION_NUMBER 0x009070cfL >> * The current library version is stored in the macro >> SHLIB_VERSION_NUMBER, >> #define SHLIB_VERSION_NUMBER "0.9.7" >> >> However: >> >> $ /sw/bin/openssl version >> OpenSSL 0.9.8h 28 May 2008 >> >> $ grep VERSION_NUMBER /sw/include/openssl/opensslv.h >> #define OPENSSL_VERSION_NUMBER 0x0090808fL >> * The current library version is stored in the macro >> SHLIB_VERSION_NUMBER, >> #define SHLIB_VERSION_NUMBER "0.9.8" >> >> Perhaps this difference contributes to the confusion? I have naively >> tried to get setup.py to print out what it considers openssl_ver by >> uncommenting line 568: >> #print 'openssl_ver = 0x%08x' % openssl_ver >> >> but due to the changed python-2.5.1.tgz, that only triggers a source >> checksum error. In order to avoid further package inconsistencies >> that could lead to much more work later, I prefer not to fiddle with >> the integrity checks.
Er wait now, python25 is 2.5.2 in unstable. No use us trying to re-fix a wheel that may already have been diagnosed and repaired (or fixed as a side-effect of something else). >> (For the same reason, I am hoping it will be possible to track down >> the issue and find a clean fix, rather than a manual workaround >> including foreign packages.) >> >> Another question is raised by >> >> $ which openssl >> /sw/bin/openssl >> >> whereas setup.py appears to look at /usr/bin/openssl first. > > That's deliberate. setup.py should be looking via /sw/lib/system-openssl, but it's a *ton* of hackery to get it to do so and gives ~no diagnostic info:( > Try removing the "openssl" package via Fink Commander or fink, and > then do another rebuild of python25. It might be that python25 gets > confused by openssl098 (we've had occasional problems with other > packages in this regard). Also openssl-dev, openssl097-dev, and openssl098-dev. Using /sw/lib/system-openssl is *supposed* to take precedence over any of those, but you're right that things can get confused, and this would rule in/out that type of problem. Also check if all of the things in /sw/lib/system-openssl are valid symlinks to things in /usr that actually exist. python25.info for 1:2.5.2-1 has the following line: SetLDFLAGS: -L%p/lib/system-openssl/lib that sometimes also helps. You the following two lines there: SetCPPFLAGS: -I%p/lib/system-openssl/include SetCFLAGS: -I%p/lib/system-openssl/include which may help setup.py find things. However, "It works for me" as-is (on 10.4.11/ppc) with various openssl*-dev installed, so I suspect interference from not-specifically-related-to-this-package unusual situation on your machine. dan -- Daniel Macks [email protected] http://www.netspace.org/~dmacks ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Fink-beginners mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.beginners
