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 brett.cannon
Recipients brett.cannon, rpetrov, skip.montanaro
Date 2008-10-02.22:03:40
SpamBayes Score 4.91639e-10
Marked as misclassified No
Message-id <>
In-reply-to <>
On Thu, Oct 2, 2008 at 1:57 PM, Roumen Petrov <> wrote:
> Roumen Petrov <> added the comment:
> One of the problems that I see in that LDFLAGS is Makefile variable and
> Makefile is part of distribution for posix build systems.
> If you set specific LDFLAGS and you want to distribute own python build
> user will get you specific settings.
> One another environment variable is OPT (if compiler don't accept -R XXX
> may be -Wl,-rpath,XXX ?) and we may use it. Also OPT environment
> variable is also Makefile variable and user specific settings will go
> into distribution too :( .
> I quick look into distutils code show that don't parse
> LDFLAGS and append environment variable LDFLAGS as is to the ldshared
> variable.
> So the first question is why parse only -L flags instead to
> pass variable value as is (aka

Because that's the use case I was supporting when I added the support;
I just needed the -L flags for compiling the extensions. If someone
writes a patch that makes it more generic it has a chance of being
checked in.

> The second question is why LDFLAGS is a Makefile variable ?

Because there is no guarantee that someone specified the envvar when
running, but if they were set for configure you know that
Python was built using those values.
Date User Action Args
2008-10-02 22:03:41brett.cannonsetrecipients: + brett.cannon, skip.montanaro, rpetrov
2008-10-02 22:03:41brett.cannonlinkissue4010 messages
2008-10-02 22:03:40brett.cannoncreate