Changes committed to git://oss.sgi.com/pcp/pcp-gui.git
VERSION | 2 +-
aclocal.m4 | 10 +++-------
debian/changelog | 7 +++++++
doc/CHANGES | 4 ++++
m4/package_utilies.m4 | 8 ++------
src/libqmc/GNUmakefile | 4 ++--
src/libqwt/GNUmakefile | 4 ++--
7 files changed, 21 insertions(+), 18 deletions(-)
commit 87c2940a2d7f6a892c29fc9f90cbb1bbc9f64c42
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed Sep 2 16:19:38 2009 +1000
Bump version number to 1.4.5 in stable branch.
commit 96874e046677d3abe80016ff9c34621d1744bb20
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed Sep 2 16:03:20 2009 +1000
Workaround another oddity in (very) recent versions of autoconf.
Problem found by the Debian autobuilders, in the pcp-gui build but it
affects pcp too. Latest versions of autoconf evaluate AC_PROG_LEX in
the compiler check macro, and complete remove any trace of AC_PROG_LEX
from its original callsite. This results in a syntax error inside our
configure script, as we call it within if ... fi, which then evaluates
to having no body to the if. Ugh. Fix is trivial though, since these
macros do the user-env-variable expansion thing already.
Resolves Debian bug #539373.
commit 7a9aaa2efbd7bd2b2a1c49c23f584a39f6aea63f
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed Sep 2 13:35:10 2009 +1000
Tighten up the SOURCES macro for libs so generated moc_* files not included.
|