Package: pkg-config
Version: 0.16.0-1
Severity: normal
With pkg-config 0.16.0-1, Gtk+ CVS HEAD's autogen.sh fails. It is unclear to
me whether the root cause of this is in pkg-config, but pkg-config is
definitively the trigger.
How to reproduce:
pbuilder create --distribution sid
pbuilder login
Inside the pbuilder chroot:
apt-get -y install vim
vim /etc/apt/sources.list # uncomment source entries
apt-get update
apt-get -y build-dep gtk+2.0
apt-get -y install automake1.7
Copy the Gtk+ CVS HEAD sources into pbuilder environment, then back in the
pbuilder environment continue with:
cd /tmp/buildd/gtk+-cvs-head
./autogen.sh
The result:
# ./autogen.sh
I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command line.
autoheader: WARNING: Using auxiliary files such as `acconfig.h',
`config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for
`config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template
without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced,
see the
autoheader: WARNING: documentation.
configure.in:133: error: possibly undefined macro: dnl
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
There is nothing obviously wrong about the use of `dnl' there:
126 AC_MSG_RESULT([$os_win32])
127
128 case $host in
129 *-*-linux*)
130 os_linux=yes
131 ;;
132 esac
133 dnl Initialize libtool
134 AC_PROG_CC
135 AM_DISABLE_STATIC
136
When repeating this with the same environment except for pkg-config downgraded
to the sarge version (0.15.0-4), autogen.sh succeeds in generating a runnable
configure script.
Also, with the original environment (i.e. with sid's pkg-config), a proper
configure script is generated when "autoconf" is called manually directly
after the failure of autogen.sh .
Please let me know if there is additional data I can contribute on this.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (800, 'unstable'), (750, 'experimental'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.7
Locale: LANG=C, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Versions of packages pkg-config depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
-- no debconf information
--
Obsig: developing a new sig
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
