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 rpetrov
Recipients brett.cannon, rpetrov, skip.montanaro
Date 2008-10-05.16:40:49
SpamBayes Score 4.88952e-09
Marked as misclassified No
Message-id <>
Lets see method customize_compiler(from 
The method search variables 'CPP', 'LDFLAGS' and 'CPPFLAGS' only in
environment. The variable CPP is not a Makefile variable. 'LDFLAGS' and
'CPPFLAGS' are makefile variables(macros). Usually makefile will export
to commands a macro only if exists environment variable with same name.
So to pass to distutils LDFLAGS is enough to to run as example
"LDFLAGS=fake make".

Issue3678 is about LDFLAGS for python shared library and now  command
start with $(LDSHARED) $(LDFLAGS) ...

If we modify Makefile to use  "...LDFLAGS=$(LDFLAGS) ..."
customize_compiler will append LDFLAGS to LDSHARED.
So this issue is about to use LDFLAGS for python modules.

Another point is that configure script append LDFLAGS to LDSHARED only
on certain platforms (all BSD based) and ignore all others.

What is preferred patch:
- a simple patch that just export LDFLAGS for;
- a patch that export LDFLAGS for all python programs, i.e. in Makefile
- a patch that append LDFLAGS to LDSHARED in configure for all platforms
and remove use of LDFLAGS in Makefile and ?
Date User Action Args
2008-10-05 16:40:51rpetrovsetrecipients: + rpetrov, skip.montanaro, brett.cannon
2008-10-05 16:40:51rpetrovsetmessageid: <>
2008-10-05 16:40:50rpetrovlinkissue4010 messages
2008-10-05 16:40:49rpetrovcreate