One of the big problems with configure is that the defines that are used to test features are not necessarily the same as the defines that are used when those features are actually used in the program being configured. Python's configure script tests for altzone, and if the defines in effect there were the same as the ones in effect during compilation, altzone would not have been found and the compilation would have gone smoothly. I don't have a solution for this problem, but a problem it is. -- Sjoerd Mullender <sjoerd.mullender@oratrix.com>
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