[issue1529269] Python 2.5b2 fails to build on Solaris 10 (GCC Compiler)
Jörg Prante added the comment: Modules/_ctypes/libffi/src/sparc/v8.S and Modules/_ctypes/libffi/src/sparc/v9.S are SPARC assembler codes. The python build process seems to pass the gcc compile flags to compile these assembler source files. It makes no sense if the debugging option -g is enabled, because C source debugging code can not be generated in the case of assembler code. The Solaris linker is also confused about this and might send the relocation / alignment errors later. So, as a workaround, just do not pass the gcc "-g" option to the python build process when building with Solaris / gcc. A clean solution would be to avoid gcc C compiler options being passed to assembler source compiling in the python build process. -- nosy: +jprante ___ Python tracker <http://bugs.python.org/issue1529269> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1
Jörg Prante added the comment: Hi Bob, thank you for your patch. I spent hours on Solaris 10 SPARC to get almost the same analysis. Just a detail, I ended up patching $LDFLAGS in the SunOS 5 part in the configure.in file (like other architectures like Darwin have set their LDFLAGS there, too). Now I'm hoping that the Python team will accept this patch. Otherwise it will be very hard and complicated for everybody else to set up a build process for a 64-bit Python together with 32-bit Python on Solaris. -- nosy: +jprante ___ Python tracker <http://bugs.python.org/issue1628484> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1
Jörg Prante added the comment: > [...] because it *still* > wouldn't follow the standards used in other OSS software, where setting > CFLAGS overrides *ALL* settings that configure may have come up with. Martin, can you please elaborate on this? I never heard of such "standards" in OSS. -- ___ Python tracker <http://bugs.python.org/issue1628484> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1
Jörg Prante added the comment: > Without knowing the impact of the generic approach you've taken > in your patch we simply cannot just apply it. If you can prove that > the patch doesn't break other platforms or configuration setups, > that would help a lot. I was able to build Python 2.5 on Solaris 10 Sparc, Mac OS X PPC, Linux PPC/Intel, all 32bit and 64bit, shared and static, only with Bob's help. It's not a proof. It's not mathematical correct. But it works. Grab all your avalaible test platforms and try for yourself what Bob's patch will 'break', and report it. Sorry, but that meta discussions about correct builds are not what a bug report should be used for. Such improvements are up to developer forums where you can design "correct" Python build scripts and discuss them over and over again. -- ___ Python tracker <http://bugs.python.org/issue1628484> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
