MacOSX compile problems

Matt Mackall mpm at selenic.com
Sat Jan 17 12:50:37 CST 2009


On Sat, 2009-01-17 at 19:30 +0100, Bastian Doetsch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> Am 17.01.2009 um 19:26 schrieb Mads Kiilerich:
> 
> > Bastian Doetsch wrote, On 01/17/2009 07:07 PM:
> >> The same: "version unknown". I guess the import error is the  
> >> reason,  but I don't understand why it happens.
> >
> > setup.py runs "hg id -it" and writes it output (or "unknown") into  
> > mercurial/__version__.py

Mads is looking at the latest unstable Mercurial which does things a
little bit differently. I'm pretty sure you're using the stable branch
as you still seem to have a version.py.

The old way involved setup.py calling mercurial/version.py which ran 'hg
identify' and then recorded its own identity. This was a little bit
over-complicated.

> hg id -it works in the mercurial directory:
> 
> $ hg id -it
> 3cc74ee75b0d tip

So now you have to figure out why it doesn't work when called from
setup.py. It almost certainly involves the environment variables PATH or
PYTHONPATH. You may also find the 'which' command enlightening. I also
suspect if you run 'hg version' -outside- the hg directory, it won't be
very happy because it doesn't happen to have the libraries it's looking
for -in the current directory-.

Or you could re-read my previous email.

-- 
http://selenic.com : development and support for Mercurial and Linux




More information about the Mercurial-devel mailing list