> gcc spit out a bunch of warnings in socketmodule.c, all of which look > to be openssl related. It's certainly possible that I have an old > openssl package laying around. It does that to me too. I think our gcc option requiring function prototypes is too picky for the openssl header files. Is there a way to teach setup.py to turn off this option when openssl is detected? It's already a separate case in setup.py. --Guido van Rossum (home page: http://www.python.org/~guido/)
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