Paul Eggert <[EMAIL PROTECTED]> writes:
> Here's the patch I installed.
Thanks for installing that. I'll reassign the Debian bug to the
documentation package.
[...]
However, let me point out a spelling error:
> +Autocoonf macros often use the @command{set} command to update
^
--
B
Getting bug-autoconf into play:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372241
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372179
> Date: Thu, 8 Jun 2006 20:09:30 +0200
> From: Julien Danjou <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: apr-util: FTBFS: cannot stat `./debian
Stepan Kasal wrote:
> Hello,
>
> On Tue, Jun 13, 2006 at 09:38:43PM +0100, William S Fulton wrote:
>> However, current and older releases of SWIG won't configure with the new
>> autoconf. Is that really intended?
>
> if the user regenerates the configure script, then yes.
>
> But released tarbal
Hello,
On Tue, Jun 13, 2006 at 09:38:43PM +0100, William S Fulton wrote:
> However, current and older releases of SWIG won't configure with the new
> autoconf. Is that really intended?
if the user regenerates the configure script, then yes.
But released tarballs usually do not require that Autoc
Hello,
On Tue, Jun 13, 2006 at 09:45:05PM +0100, William S Fulton wrote:
> @top_builddir@ used to expand to ../../../
> now it expands to ../../..
> Parts of our Makefiles were relying on the trailing slash, so they don't
> work with this version of autoconf. Is this change also intentional?
yes,
Ben Pfaff <[EMAIL PROTECTED]> writes:
> In the long term, I suspect that the Autoconf macros in the
> apr-util package should be fixed, and that autoconf-doc should
> document that $@ may be changed by some macros.
I've done the latter by installing the patch at the end of this
message into Autoc
William S Fulton <[EMAIL PROTECTED]> writes:
> @top_builddir@ used to expand to ../../../
> now it expands to ../../..
> Parts of our Makefiles were relying on the trailing slash, so they don't
> work with this version of autoconf. Is this change also intentional?
I'm afraid that's true as well.
William S Fulton <[EMAIL PROTECTED]> writes:
> However, current and older releases of SWIG won't configure with the new
> autoconf. Is that really intended?
I'm afraid so. From the NEWS file:
* Some directory variables have been added, and others adjusted to
changes in the GNU Coding Standard
Ralf Wildenhues wrote:
> GNU Autoconf test version 2.59d is now available.
>
> This is a beta release, intended to be largely identical to 2.60,
> to be released very soon, if no unexpected issues turn up. So test it
> now, use it with your code, and report any remaining issues, please!
>
> T
This version of autoconf breaks our configure.in script. This is what we
have...
configure.in:
AC_ARG_WITH(swiglibdir,[ --with-swiglibdir=DIR Put SWIG
system-independent libraries into DIR.],
[swig_lib="$withval"], [swig_lib="${datadir}/swig/${PACKAGE_VERSION}"])
AC_SUBST(swig_lib)
AC_DEFINE
I've seen a flurry of Debian BTS emails around this bug, but none
of them have made it clear to me what I should do about it.
In the long term, I suspect that the Autoconf macros in the
apr-util package should be fixed, and that autoconf-doc should
document that $@ may be changed by some macros.
11 matches
Mail list logo
