Chris,
> Read my previous posts. The problem is not with the lines above for the
> includes or libraries, but with commands like
>
> pythonvers=`python -c 'import sys; sys.stdout.write(sys.version[:3])'`
only thing that this does, is to add more possible directories to the set from which the selection is made, but the given incdir and libdir will have precedence if they point to an actual Python.h and Python. Neither Python.h nor Python is versioned other than the directory location which you are giving explicitly.
> in the ./configure script that have a hardcode assumption that to run
> python the executable name is 'python'. I need to be able to change this,
> as well as the include and lib. So in effect run
But if the correct incdir and libdir are given, pythonvers is irrelevant in the case you have described so far. Hence, why does it need changing?
In the original example that you sent, you gave the wrong libdir. If anything, perhaps it should just spit out an error instead of defaulting to the system, but adding a version doesn't change the fact it was the wrong libdir.
> Unless I have missed it, there is no option in the configure script to
> change this ?
No, there isn't AFAIK. Feel free to sent a patch to rootdev.
Best regards,
Wim
-- WLavrijsen_at_lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.netReceived on Wed Sep 14 2011 - 20:38:27 CEST
This archive was generated by hypermail 2.2.0 : Wed Sep 14 2011 - 23:50:01 CEST