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

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()

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()

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 (

Re: install-local target?

Hello Karl, * Karl Berry wrote on Sat, Apr 11, 2009 at 02:54:16AM CEST: > 1) In the Extending node of the automake (1.10.2) manual, there's a typo: > > now: respected by `automake' to ensure the user always have the last word. > new: respected by `automake' to ensure the user always has the last

Re: debugging feature for recursive rules

Hi Karl, thanks for the report. * Karl Berry wrote on Sat, Apr 11, 2009 at 02:54:16AM CEST: > I have found myself needing to go through the complicated shell > sequence for the $(RECURSIVE_TARGETS) rule more than once when debugging > the Makefile.am's in a big directory tree (namely TeX Live).