% uname -a
HP-UX td176 B.11.23 U ia64 1928826293 unlimited-user
license

% cc -V
cc: HP aC++/ANSI C B3910B A.06.07 [Feb 2 2006]

env CC=cc CXX=aCC ./configure
--prefix=/var/tmp/rwgk/py25a1 --without-gcc
make

The output of make ends with:

  No such file or directory: python
  *** Error exit code 127

  Stop.

I'll upload the full output of configure and make.

Note that the testdrive machine is publically accessible:

http://www.testdrive.hp.com/
telnet td176.testdrive.hp.com

Logged In: YES 
user_id=29957



If you put a '-' at the start of the line in the Makefile,
it should build ok. Make it:

$(AST_H) $(AST_C): $(AST_ASDL) $(ASDLGEN_FILES)
        -$(ASDLGEN) $(AST_ASDL)

Obviously there's some issues with timestamps on the files
and it's trying to rebuild the file unnecessarily...

Logged In: YES 
user_id=29957

Right. Python.asdl and the output files that depend on it
have the same timestamps in the tarball. This is because
they get updated and all checked in in the same svn
revision. When the export is done, the timestamps are set to
the same time. 

Possible solutions:
  - make ignores this failure. Bad, because it might stop
_real_ errors.
  - make catches lack of Python, and skips the step. Ugly,
and hard to do in a platform-compatible way.
  - I change the 'welease.py' script to adjust the
timestamps of the files before making the release tarballs.
 This is so nasty it makes me sick. But I can't see a better
option. 

Logged In: YES 
user_id=71407

I get a complete build if I

touch Include/Python-ast.h Python/Python-ast.c

before running configure. If you wait a second after the svn
export and then touch these two files I'd expect the tarball
to work out of the box.

Another idea is to work with MD5 signatures, like SCons
does. But if you don't have a Python yet it is probably
difficult to find a fully portable solution.

Logged In: YES 
user_id=21627

The welease script should check that the exported time
stamps are already in the right sequence (i.e.
Python-ast.[ch] newer than their dependencies). If this is
not the case, a commit should be forced on the file that is
too old. Then, if the files don't change before the next
release, no time stamp changing will be necessary.

Logged In: YES 
user_id=29957

The welease tool now does the right thing to touch the files
before building the tarballs.