Skip Menu |
 

To: krb5-bugs@mit.edu
From: Sam Hartman <hartmans@MIT.EDU>
Subject: mainline util/reconf does not work
Date: Wed, 6 Nov 2002 17:13:57 -0500 (EST)
Download (untitled) / with headers
text/plain 1.2KiB

I get the following output on a Debian system:

hartmans@solipsist-nation:src(12)> ./util/reconf --force
Remaking all configuration files
Using autoconf version 2.53 found in your path...
Patching autoreconf
About to patch /usr/bin/autoreconf to ...
/tmp/autoreconf30187: use: command not found
/tmp/autoreconf30187: use: command not found
/tmp/autoreconf30187: use: command not found
/tmp/autoreconf30187: use: command not found
/tmp/autoreconf30187: line 8: syntax error near unexpected token `{'
/tmp/autoreconf30187: line 8: `if ($0 =~ /autoconf$/) {'


hartmans@solipsist-nation:src(14)> dpkg -l autoconf*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii autoconf 2.53-2 automatic configure script builder
ii autoconf2.13 2.13-43 automatic configure script builder (obsolete


One issue that may be problematic here is that Debian has the autoconf
scripts try to determine whether autoconf 2.5 or 2.13 should be used
if both are installed, so /usr/bin/autoreconf may not be what you
expect.
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #1242] mainline util/reconf does not work
From: Sam Hartman <hartmans@mit.edu>
Date: Wed, 06 Nov 2002 17:53:19 -0500
RT-Send-Cc:

After working around the patching the wrong autoreconf, I find that
Debian misdetects our autoconf scripts as 2.13 scripts.

Debian requires either that you use configure.ac or you use AC_PREREQ
in configure.in--aclocal is not sufficient.

This does seem a bit broken on Debian's part, but unfortunately it is
in a stable release so it isn't getting fixed any time soon.


One option is to say we don't support building 1.3 on Debian 3.0.

We could also add AC_PREREQ to all the configure.in scripts in the tree.
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #1242] mainline util/reconf does not work
From: Sam Hartman <hartmans@mit.edu>
Date: Wed, 06 Nov 2002 18:53:32 -0500
RT-Send-Cc:
OK, this bug is mostly unfixable. Debian's autoreconf passes options
to Debian's autoconf that Debian's autoconf fails to understand.
Apparently the wrapper script doesn't grok --include even if it ends
up calling autoconf 2.50.
Sam,

There may be a way to make things work. Does debian install
something like autoreconf253? I.e. with the version number appended?

We might be able to set it up that we test for
autoreconf with the version number of autoconf appended and run that
one (or a patched one) explicitly. Or we could make it debian specific.

Ezra
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #1242] mainline util/reconf does not work
From: Sam Hartman <hartmans@mit.edu>
Date: Thu, 07 Nov 2002 13:33:20 -0500
RT-Send-Cc:
Show quoted text
>>>>> "Ezra" == Ezra Peisach via RT <rt-comment@krbdev.mit.edu> writes:

Show quoted text
Ezra> Sam, There may be a way to make things work. Does debian
Ezra> install something like autoreconf253? I.e. with the version
Ezra> number appended?

Yes, but the autoreconf2.50 that Debian installs converts --localdir
into --include, then calls autoconf (unqualified with no version
number) which is a wrapper script that does not understand --include.

I think what I'd recommend for people on Debian 3.0 is set up a
directory including autoconf, autoheader, autoreconf and aclocal as
symlinks to the versioned versions of these programs and stick that
directory at the top of your path.
Subject: mainline util/reconf does not work on debian
There are a couple issues with assumptions we make about the autoreconf
script that could be cleaned up (1: it's a /bin/sh script and not perl;
2: it doesn't care if it's name is not precisely "autoreconf") to make
debian's autoreconf happier, but the --localdir/--include argument
breakage is something we cannot easily work around. It's a Debian bug.

(I've tweaked the ticket subject to indicate it's on Debian only. I'm
not aware of other systems shipping similarly hacked autoconf, but that
doesn't mean they're not out there....)
Subject: Bug#178257: [krbdev.mit.edu #1242] Autoconf2.13 package does not support -I to autoreconf
To: submit@bugs.debian.org
Date: Fri, 24 Jan 2003 13:56:04 -0500 (EST)
From: hartmans@mit.edu (Sam Hartman)
RT-Send-Cc:
package: autoconf2.13

Hi. I'm one of the developers for MIT Kerberos and I was trying to
build Kerberos on Debian 3.0.

I ran into the problem that the autoconf script in the autoconf2.13
package does not understand the -I option to include a directory
containing additional macros. This is somewhat understandable because
the old 2.13 version of autoconf only has --localdir, not -I.

But it seems that when calling autoconf 2.50, the Debian script should
support all the autoconf 2.50 options.


I could work around this, except that autoreconf2.50 will convert
--localdir into -I and then call an unqualified autoconf instead of
calling autoconf2.50.

So, I think there is no way I can use --localdir with an autoconf 2.50
project and have autoreconf work for that project.
To: rt@krbdev.mit.edu
Subject: [krbdev.mit.edu #1242] Possible to fix now
Date: Thu, 6 Feb 2003 14:14:11 -0500 (EST)
From: hartmans@mit.edu (Sam Hartman)
RT-Send-Cc:


The autoconf2.13 packages in testing and unstable no longer have the
impossible to work around bug. If we add AC_PREREQ and prefer
autoreconf2.50 to autoreconf (or provide a way not to modify the
system autoconf at all for 2.57)e, Debian will work fine.


Ken said he could add the AC_PREREQ calls so I'm bouncing this to him.
Download (untitled) / with headers
text/plain 1.2KiB
Sam, using the autoconf 2.57 you installed on sfdf, I have no problems
with the configure.in files as they are.

There is a minor problem with aclocal.m4 and the configure scripts it
had generated for me on my system before I ran them on sfdf:

We decide whether --include or --localdir is supported by looking for a
macro defined in 2.54 or whatever the point was where --localdir stopped
being accepted. That test happens when m4 is run, the result gets put
into the configure script, then into the generated makefiles, and is
eventually used when running autoconf (if that's ever needed). The
problem is, the autoconf run at that point may not be the one originally
used to generate the current configure scripts. The configure scripts I
produced with autoconf 2.53 generated makefiles that specified the use
of --localdir, but 2.57 on sfdf didn't accept that option.

Running util/reconf on sfdf fixed the problem, so it's not a big deal.

If we want to fix it, I think requiring 2.53 and always using --include
will take care of it. (The --include option wasn't introduced until
2.53, I believe.) Well, long term, I think we definitely want to fix
it; question is, is it important for 1.3? It's a small problem, but
should be a small change to fix it.
From: raeburn@mit.edu
Subject: CVS Commit
Simplify autoconf compatibility by requiring that we always have a version that
supports --include, instead of assuming that whether the autoconf to be run
supports it is the same as whether the autoconf used to generate the current
configure scripts supported it.

* aclocal.m4: Require autoconf 2.53.
(CONFIG_RULES): Always set AUTOCONFINCFLAGS to --include.


To generate a diff of this commit:



cvs diff -r5.407 -r5.408 krb5/src/ChangeLog
cvs diff -r1.257 -r1.258 krb5/src/aclocal.m4
From: raeburn@mit.edu
Subject: CVS Commit
* reconf: Drop support for 2.52 and earlier.


To generate a diff of this commit:



cvs diff -r1.122 -r1.123 krb5/src/util/ChangeLog
cvs diff -r1.17 -r1.18 krb5/src/util/reconf
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #1242] CVS Commit
From: Sam Hartman <hartmans@mit.edu>
Date: Thu, 24 Apr 2003 15:38:47 -0400
RT-Send-Cc:

I think this is the second time someone has dropped support for
Autoconf 2.52. We cannot do that; OSX only has 2.52.
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #1242] CVS Commit
From: Ken Raeburn <raeburn@MIT.EDU>
Date: Thu, 24 Apr 2003 15:55:56 -0400
RT-Send-Cc:
Yes, Tom also pointed this out to me. I'll be backing out the change,
maybe find another way to deal with the problem....
From: raeburn@mit.edu
Subject: CVS Commit
Require only autoconf 2.52. Try --include argument to autoconf and autoheader,
and if the command fails, try it again with --localdir; don't tie it to some
previously used version of autoconf.


To generate a diff of this commit:



cvs diff -r5.408 -r5.409 krb5/src/ChangeLog
cvs diff -r1.258 -r1.259 krb5/src/aclocal.m4
cvs diff -r5.181 -r5.182 krb5/src/config/ChangeLog
cvs diff -r1.48 -r1.49 krb5/src/config/post.in
cvs diff -r1.351 -r1.352 krb5/src/include/ChangeLog
cvs diff -r1.47 -r1.48 krb5/src/include/Makefile.in
From: raeburn@mit.edu
Subject: CVS Commit
* reconf: Restore support for 2.52; reject older versions.


To generate a diff of this commit:



cvs diff -r1.123 -r1.124 krb5/src/util/ChangeLog
cvs diff -r1.18 -r1.19 krb5/src/util/reconf
From: tlyu@mit.edu
Subject: CVS Commit
pullup from trunk


To generate a diff of this commit:



cvs diff -r5.403.2.4 -r5.403.2.5 krb5/src/ChangeLog
cvs diff -r1.253.2.4 -r1.253.2.5 krb5/src/aclocal.m4
cvs diff -r5.180.2.1 -r5.180.2.2 krb5/src/config/ChangeLog
cvs diff -r1.48 -r1.48.2.1 krb5/src/config/post.in
cvs diff -r1.121.2.1 -r1.121.2.2 krb5/src/util/ChangeLog
cvs diff -r1.16.2.1 -r1.16.2.2 krb5/src/util/reconf