> BTW: I've been doing gcc pre-release testing regularly for many year, starting > with gcc 3.3. This is the first time I see the Python build fail persistently > for several weeks. Wild guess: did configure detect that it needs to use -fno-strict-aliasing? 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