Package: automake Version: 1:1.11.1-1 Severity: normal (also impacts automake-1.9)
A rule-variable of the following form: > foo: VAR=whatever ... is mistaken by automake by a custom production rule for "foo", and it does not generate a production rule itself. I could work around this behaviour with something like: > EMPTY= > foo$(EMPTY): VAR=whatever Note: I needed that for a crossbuild, where some libraries have to be built both for host and target. libnativefoo.a needs different LDFLAGS and RANLIB definitions which automake does not apparently allows to change. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34.1-00003-ge5b0813-dirty (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages automake depends on: ii autoconf 2.67-2 automatic configure script builder ii autotools-dev 20100122.1 Update infrastructure for config.{ ii dpkg 1.15.8.4 Debian package management system ii install-info 4.13a.dfsg.1-5 Manage installed documentation in automake recommends no packages. automake suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org