Issue 766210: Mac/OSX/Makefile assumes case-insensitive build (original) (raw)

Issue766210

Created on 2003-07-04 23:33 by jackjansen, last changed 2022-04-10 16:09 by admin. This issue is now closed.

Messages (3)
msg16883 - (view)	Author: Jack Jansen (jackjansen) *	Date: 2003-07-04 23:33
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. --------------
msg16884 - (view)	Author: Jack Jansen (jackjansen) *	Date: 2003-07-21 21:45
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.
msg16885 - (view)	Author: Jack Jansen (jackjansen) *	Date: 2004-07-16 10:48
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.