Re: python.m4 macro does pass unexpanded argument to get_python_lib()

2009-04-16 Thread Matthias Klose
Ralf Wildenhues schrieb: > Hello Matthias, > > * Matthias Klose wrote on Tue, Apr 14, 2009 at 09:02:27AM CEST: >> seen in 1.10.1. >> >> '${prefix}' and '${exec_prefix}' are passed unexpanded to get_python_lib()), >> and >> the macro then defaults to the hardcoded alternative case. The patch passe

Re: python.m4 macro does pass unexpanded argument to get_python_lib()

2009-04-14 Thread Ralf Wildenhues
Hello Matthias, * Matthias Klose wrote on Tue, Apr 14, 2009 at 09:02:27AM CEST: > seen in 1.10.1. > > '${prefix}' and '${exec_prefix}' are passed unexpanded to get_python_lib()), > and > the macro then defaults to the hardcoded alternative case. The patch passes > the > real path names to get_p

Re: python.m4 macro does pass unexpanded argument to get_python_lib()

2009-04-14 Thread Matthias Klose
Matthias Klose schrieb: > seen in 1.10.1. > > '${prefix}' and '${exec_prefix}' are passed unexpanded to get_python_lib()), > and > the macro then defaults to the hardcoded alternative case. The patch passes > the > real path names to get_python_lib(), and only for the case, where the prefix > ar

python.m4 macro does pass unexpanded argument to get_python_lib()

2009-04-14 Thread Matthias Klose
seen in 1.10.1. '${prefix}' and '${exec_prefix}' are passed unexpanded to get_python_lib()), and the macro then defaults to the hardcoded alternative case. The patch passes the real path names to get_python_lib(), and only for the case, where the prefix argument was specified on the command line (