Skip Montanaro wrote: > Andrew> We therefore have to have flags that will force HP to compile > Andrew> for some common generic processor. > > Skip> Can you submit a patch with these changes? > > Cameron> You're losing me, Skip. What, to you, would constitute "a > Cameron> patch"? > > Probably a patch to configure.in. We set lots of platform- or OS-specific > compilation flags there. > > Skip > My lack of experience with configure make it hard to submit a patch, so I'll ask python-dev first. If that's too much I'll have a go, but it will take a while. These are the settings that we use: HP/RISC 32-bit: c89 -c +DA2.0 +DS2.0 +Z -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT aCC -c +DA2.0 +DS2.0 +Z -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT aCC +DA2.0 +DS2.0 +Z -Wl,+s -Wl,+k ... -lpthread HP/RISC 64-bit: c89 -c +DA2.0W +DS2.0a +Z -D_REENTRANT aCC -c +DA2.0W +DS2.0a +Z -D_REENTRANT aCC +DA2.0W +DS2.0a +Z -Wl,+s -Wl,+k ... -lpthread HP/ITANIUM 64-bit: cc -c +DD64 +DSitanium2 -Ae -mt -D_POSIX_C_SOURCE=199506L aCC -c +DD64 +DSitanium2 -AP -mt aCC +DD64 +DSitanium2 -AP -mt -Wl,+k -Wl,+s NOTE: the multithreading flags (-D_REENTRANT -mt) should only be applied to the files where there is actually threaded code. When applied to all files indiscriminately, they cause overall performance degradation. AFAIK the files with threaded code are: thread.c threadmodule.c We also found that if the build is linked without specifying the thread library, the build appears fine, but threading doesn't happen at run-time. Andrew MacKeith > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/mackeith%40acm.org >
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