[issue11946] 2.7.1 'test_commands' build test fails

[Jason Vas Dias]

Jason Vas Dias <jason.vas.dias at gmail.com> added the comment:

The alternative is to use a "GCC Spec File" , such as
that printed by 
 $ gcc -dumpspecs

Here is one such I've used in the past to overcome similar problems:

$ cat /home/jason/local32.spec
*lib:
+ -lc_nonshared

*startfiles:
+ /lib32/crti.o

*endfiles:
+ /lib32/crtn.o

*link:
+ -dynamic-linker /usr/local/lib%{!m32:64}%{m32:32}/ld-linux-%{!m32:x86_64}%{m32:i386}.so.2 -L/usr/local/lib/gcc-lib/%{!m32:x86_64-redhat-linux}%{m32:i386-redhat-linux}/4/%{m32:32} -L/usr/local/lib/%{!m32:64}%{m32:32} -R/usr/local/lib/gcc/%{!m32:x86_64-redhat-linux}%{m32:i386-redhat-linux}/4 -R/usr/local/lib%{m32:32}%{!m32:64} -R/usr/local/lib

*cpp:
+ -isystem /usr/local/include

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11946>
_______________________________________