[issue12346] Python 2.7.2 source code build (release) depends on mercurial

Ezio Melotti added the comment: The regexes are now in the right order. -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

Changes by Santoso Wijaya : -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

R. David Murray added the comment: That needs to be ported to the other branches, then. Ezio, on a completely unrelated note, notice what happened to Ralf's reference. I think the regexes may need to be reordered. -- nosy: +ezio.melotti ___ Python

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

Ralf Schmitt added the comment: trunk configure.in contains code that checks for the existence of a .hg repository. See rev 435eec7b41f0 -- nosy: +schmir ___ Python tracker ___

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

R. David Murray added the comment: Ah. For subversion there was a similar check, and the values were set to blank if the subversion binary was not found. For hg it looks like we need to add additional checks on whether or not there is a repo. (We can probably assume that if there is a repo

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

R. David Murray added the comment: Indeed, I just confirmed that building with a recent version of mercurial installed from the release 2.7.2 source tarball from python.org, the make results in: abort: repository . not found! abort: repository . not found! abort: repository . not found! duri

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

R. David Murray added the comment: It used to be that the svn version info was pulled from embedded constants in Makefile.pre.in. I agree that depending on having mercurial (and, presumably, a repo!) at build time is wrong. These constants need to be pre-computed when a release tarball is b

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

Graeme Winter added the comment: Some more information: It has picked up that I have mercurial installed: [gw56@ws050 Python-2.7.2_cci]$ cat config.log | grep HG ac_cv_prog_HAS_HG=found HAS_HG='found' HGBRANCH='hg id -b $(srcdir)' HGTAG='hg id -t $(srcdir)' HGVERSION='hg id -i $(srcdir)' ho

[issue12346] Python 2.7.2 source code build (release) depends on mercurial

New submission from Graeme Winter : Trying to build 2.7.2 from source on RHEL5 32 bit get errors: gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE \ -DSVNVERSION="\"`LC_ALL=C svnversion .`\""