This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jprante
Recipients jprante, nnorwitz, ostkamp, theller
Date 2009-01-04.14:00:07
SpamBayes Score 5.925063e-06
Marked as misclassified No
Message-id <1231077609.22.0.794565048839.issue1529269@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2009-01-04 14:00:09jprantesetrecipients: + jprante, nnorwitz, theller, ostkamp
2009-01-04 14:00:09jprantesetmessageid: <1231077609.22.0.794565048839.issue1529269@psf.upfronthosting.co.za>
2009-01-04 14:00:08jprantelinkissue1529269 messages
2009-01-04 14:00:07jprantecreate