[ python-Bugs-766210 ] Mac/OSX/Makefile assumes case-insensitive build

[SourceForge.net]

Bugs item #766210, was opened at 2003-07-05 01:33
Message generated for change (Comment added) made by jackjansen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=766210&group_id=5470

Category: Macintosh
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 3
Submitted By: Jack Jansen (jackjansen)
Assigned to: Jack Jansen (jackjansen)
Summary: Mac/OSX/Makefile assumes case-insensitive build

Initial Comment:
Mac/OSX/Makefile doesn't work on a case-sensitive 
filesystem, because it assumes that python.exe exists. 
Here's a fragment of an email conversation on the topic:
----------------
1) In the top level Makefile, BUILDEXE is set depending on 
whether the filesystem is case insensitive or not.  However, 
Mac/OSX/Makefile always assumes case-insensitivity, so 
there can be a conflict if python is built under Mac OS X on 
UFS or NFS.

This is unintentional. But: I don't have a UFS file system 
handy right now, and visual inspection
of Mac/OSX/Makefile hasn't revealed any obvious things. 
Could you elaborate? If all else fails send me the diff, after 
going through the release process.

Sorry I wasn't more clear.  It is the following line in Mac/
OSX/Makefile that is the problem:

BUILDPYTHON=$(builddir)/python.exe

This expects the top level Makefile to have added a .exe 
suffix, which would only happen if a case-insensitive 
filesystem was detected.
--------------

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

>Comment By: Jack Jansen (jackjansen)
Date: 2004-07-16 12:48

Message:
Logged In: YES 
user_id=45365

Tried a build on a UFS filesystems and there were no problems: the 
toplevel Makefile communicates the correct BUILDPYTHON to Mac/OSX/
Makefile.

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

Comment By: Jack Jansen (jackjansen)
Date: 2003-07-21 23:45

Message:
Logged In: YES 
user_id=45365

I am at loss to why this problem still exists. On inspection it 
seems to be a duplicate of #677753, which was fixed 6 months 
ago, so the problem shouldn't have showed up in 2.3b2.

I will not fix this bug for 2.3, and try to find out what is going on.

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

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