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

[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 passes 
>> the
>> real path names to get_python_lib(), and only for the case, where the prefix
>> argument was specified on the command line (the case for a missing prefix
>> argument is handled inside the get_python_lib() function).
>>
>> tested the macro with python versions 2.0 up to trunk, and the 3.0 and 3.1 
>> branches.
> 
> Thanks for the report.  This is <http://bugs.debian.org/523030>.
> Please answer the questions I asked you there.

closed this report.

I openend a new one as http://bugs.debian.org/524176 with a new patch, which
does pass a valid path to get_python_lib() and then repaces the prefix with the
unexpanded macro again. this doesn't change the current behaviour, but does
allow get_python_lib() to look at a valid path.

  Matthias