Bugs item #1558802, was opened at 2006-09-14 10:51
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1558802&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: Installation
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Ralf W. Grosse-Kunstleve (rwgk)
Assigned to: Nobody/Anonymous (nobody)
Summary: Tru64 make install failure

Initial Comment:
"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


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1558802&group_id=5470
_______________________________________________
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to