> John Abel <johnfabel@btinternet.com> writes: > > > Just a quick update. As a final attempt, before I implemented > > Martin's suggestion, I chaged the order of the includes. > > Then you are operating Python out of its specification. See > > http://www.python.org/doc/current/api/includes.html > > Good luck, and be prepared for random crashes. > > > Having Python.h last in the includes, solved everything (apart from > > a warning, about _FILE_OFFSET_BITS being redefined. If it's already > > defined by the OS, does pyconfig.h have to define it?). Is there > > somewhere to log things such as this? Does it warrant a bug report? > > There is no bug AFAICT. > OK, I can see why Python.h has to be first, but surely, abiding by the spec shouldn't prevent code from executing properly? Should I raise a bug report for this? I'm guessing that only Solaris is affected (though maybe other BSD-types are, too? AFAIK, only Solaris has the /proc oddity). I'd like to be able to produce compliant modules. I'd like to help, if I can. Regards John
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