[ python-Bugs-969718 ] BASECFLAGS are not passed to module build line

SourceForge.net noreply at sourceforge.net
Fri Jan 13 22:19:32 CET 2006


Bugs item #969718, was opened at 2004-06-09 10:56
Message generated for change (Comment added) made by nyogtha
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=969718&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Distutils
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Jason Beardsley (vaxhacker)
Assigned to: Nobody/Anonymous (nobody)
Summary: BASECFLAGS are not passed to module build line

Initial Comment:
The value of BASECFLAGS from
/prefix/lib/pythonver/config/Makefile is not present on
the compile command for modules being built by
distutils ("python setup.py build").  It seems that
only the value of OPT is passed along.

This is insufficient when BASECFLAGS contains
"-fno-static-aliasing", since recent versions of gcc
will emit incorrect (crashing) code if this flag is not
provided, when compiling certain modules (the mx
products from egenix, for example).

I did try to set CFLAGS in my environment, as directed
by documentation, but this also had zero effect on the
final build command.


----------------------------------------------------------------------

Comment By: nyogtha (nyogtha)
Date: 2006-01-13 15:19

Message:
Logged In: YES 
user_id=1426882

This is still a bug in Python 2.4.2.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=969718&group_id=5470


More information about the Python-bugs-list mailing list