On Thu, Jun 09, 2011 at 03:12:42PM +0200, Jiri Denemark thus spake:
On Thu, Jun 09, 2011 at 20:55:01 +0800, Daniel Veillard wrote:
> > another way would be to launch python directly giving the path to the
> > python script, this is likely to solve the issue there.
That IMHO avoids the problem completely and I doubt anybody would
complain
I agree, and we already use that in one place in python/Makefile.am:
$(PYTHON) $(srcdir)/$(GENERATE) $(PYTHON)
we should even be able to detect at configure and take specific
paths if people want to use a non-system python binary by extending
paphio:~/libvirt -> ./configure --help | grep python
--with-python Build python bindings [default=yes]
to take a path
No extension needed, it already supports that (although it's not advertised
anywhere). One can use the following forms
--with-python
--with-python=/usr/local
--with-python=/usr/local/bin/python
PYTHON=/usr/local/bin/python --with-python
Jirka
Sounds good to me. How would the python script in question support this?
Thanks,
Jason
--
Jason Helfman
System Administrator
experts-exchange.com
http://www.experts-exchange.com/M_4830110.html
E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list