On Wed, 9 Oct 2002, Barry A. Warsaw wrote: > > >>>>> "TR" == Tim Rice <tim@multitalents.net> writes: > > TR> The -R flag in not supported on all systems. > TR> 2.2.2b1 build is broken on SCO Open Server now too. > > Shouldn't distutils be taught what to do with runtime_library_dirs for > SCO and MacOSX? It gets tricky trying to automagicly use the -R flag. As an example, the default install dir for OpenSSL is /usr/local/ssl. So on platforms that support -R you would think you could use -L/usr/local/ssl/lib -R/usr/local/ssl/lib -lssl -lcrypto OpenUNIX supports -R but if you did not build shared libraries for OpenSSL, the -R/usr/local/ssl/lib will break the build. Then there is the whole issue of what non system dirs to include. Maybe you have OpenSSL 0.9.6g in /usr/local/ssl but you're testing 0.9.7 that's installed in some other dir. If setup.py automagicly adds ssl to build the '_socket' extension, how does it know which version to use? How would it even find the one not in /usr/local/ssl? Normally you would configure --with-ssl-dir=/some_path_to_ssl As one who has done ports to many Open Source projects, I found python one of the more difficult ones because the build process uses python. So for a new platform (or broken build) you have to know python to build python. > > -Barry > -- Tim Rice Multitalents (707) 887-1469 tim@multitalents.net
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4