The fact that Python installs its config.h as <prefix>/python2.0/config.h is annoying if one tries to combine Python with some other autoconfiscated package. If you configure that other package, it detects that it needs to add -I/usr/local/include/python2.0; it also provides its own config.h. When compiling the files #include "config.h" could then mean either one or the other. That can cause quite some confusion: if the one of the package is used, LONG_LONG might not exist, even though it should on that port. This issue can be relaxed by renaming the "config.h" to "pyconfig.h". That still might result in duplicate defines, but likely SIZE_FLOAT (for example) has the same value in all definitions. Regards, Martin
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