"make install" of Python 2.5c2 fails under Tru64 Unix
V5.1. The failure is fixed by the simple patch below.
I.e., simply remove two lines from Makefile.pre.in.
Apparently the native make doesn't support comments
where commands are expected.


diff -r -u Python-2.5c2/Makefile.pre.in
Python-2.5c2_cci/Makefile.pre.in
--- Python-2.5c2/Makefile.pre.in        2006-07-30
09:20:10.000000000 -0700
+++ Python-2.5c2_cci/Makefile.pre.in    2006-09-14
10:17:12.000000000 -0700
@@ -850,8 +850,6 @@
        $(INSTALL_DATA) Modules/Setup.config
$(DESTDIR)$(LIBPL)/Setup.config
        $(INSTALL_SCRIPT) $(srcdir)/Modules/makesetup
$(DESTDIR)$(LIBPL)/makesetup
        $(INSTALL_SCRIPT) $(srcdir)/install-sh
$(DESTDIR)$(LIBPL)/install-sh
-       # Substitution happens here, as the
completely-expanded BINDIR
-       # is not available in configure
        sed -e
"s,@EXENAME@,$(BINDIR)/python$(VERSION)$(EXE)," <
$(srcdir)/Misc/python-config.in >python-config
        $(INSTALL_SCRIPT) python-config
$(DESTDIR)$(BINDIR)/python$(VERSION)-config
        rm python-config

Logged In: YES 
user_id=33168

Assigning to Anthony so he sees this.

Not sure if this is appropriate here but it may at least indicate that the issue is affecting more than one user. I've just come across this bug and implementing the suggested patch fixed the issue for me. 
My company has a lot of DEC Alpha's (uname -a: OSF1 <hostname> V4.0 1530 alpha) that we want to run Python on. It would be great if this simple fix was rolled into the main baseline in a future release.

Ralf, Chris, is this still an issue?

Feedback from issue 727732 makes me believe this is a pretty ancient
platform, so I'll close this if no interested parties voice their
opposition.

It is no longer a problem for me. As of last fall, we don't have any
Tru64 machines anymore.

Thanks for the feedback, Ralf.