[Python-bugs-list] [Bug #130165] Python 2.1a1 Makefile changed OPT value not used in module c

[noreply@sourceforge.net]

Bug #130165, was updated on 2001-Jan-26 06:46
Here is a current snapshot of the bug.

Project: Python
Category: None
Status: Closed
Resolution: Fixed
Bug Group: None
Priority: 5
Submitted by: nobody
Assigned to : akuchling
Summary: Python 2.1a1 Makefile changed OPT value not used in module c

Details: When the top level "Makefile" value used for the variable "OPT" is
changed
after executing "configure", that new value is used to compile "python",
but is *not* used during the compilation of the modules.


Follow-Ups:

Date: 2001-Feb-14 09:30
By: akuchling

Comment:
No comment from original submitter -- assuming this bug 
is obsolete.
-------------------------------------------------------

Date: 2001-Feb-07 14:37
By: akuchling

Comment:
Yes, but in 2.1alpha2 nothing should be doing 'cd Modules' at all, which is
why I'd like to know if it happens with either alpha2 or the current CVS
tree.

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

Date: 2001-Jan-30 00:47
By: nobody

Comment:
Updated more details by original submitter:

The problem appears shortly after a "cd Modules" but shows up only
during compilation of the ".so" extension modules.  The first module
compilation in the original 2.1a1 version to show the failure to use the
changed value of "OPT" follows the line:

	"building 'regex' extension"

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

Date: 2001-Jan-28 19:19
By: nobody

Comment:
I can't replicate this; when I edit the Makefile, the new OPT setting
is picked up by the setup script.  Does it still happen with the current
CVS version?
-------------------------------------------------------

Date: 2001-Jan-26 07:45
By: nascheme

Comment:
Hmm, perhaps the makefile could pass OPT to the distutils
setup.py script.  Andrew knows better than I how to solve
this.

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

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=130165&group_id=5470