MacOSX compile problems
bastian.doetsch at gmx.de
Sat Jan 17 20:02:17 CST 2009
First I'd like to thank you for trying to solve this :).
Unfortunately, I still haven't found a solution.
> 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.
I'm running (afaik) latest crew-tip, so it should be the same that
$ hg log -l1
user: Patrick Mezard <pmezard at gmail.com>
date: Tue Jan 13 20:28:06 2009 +0200
summary: diffstat: don't fail on merges
> The old way involved setup.py calling mercurial/version.py which ran
> identify' and then recorded its own identity. This was a little bit
>> 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
> very happy because it doesn't happen to have the libraries it's
> for -in the current directory-.
Having been enlightened at work a few years ago, I already tried the
"which" command. As I posted before, the install seems to work fine:
$ which python
$ which hg
My path is:
Actually, I can run hg version in every directory I choose - it
doesn't complain and hg just works. Only the make/install doesn't...
> Or you could re-read my previous email.
... and come to what conclusion? After re-reading and not spotting
anything I overlooked, it seems like I don't understand correctly,
what you were saying.
Thanks for the help, though
> http://selenic.com : development and support for Mercurial and Linux
More information about the Mercurial-devel