[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fix for fugly autoconf 2.62 bug
From: |
Mike Frysinger |
Subject: |
Re: fix for fugly autoconf 2.62 bug |
Date: |
Tue, 22 Apr 2008 02:09:22 -0400 |
User-agent: |
KMail/1.9.7 |
On Tuesday 22 April 2008, Ralf Wildenhues wrote:
> * Eric Blake wrote on Mon, Apr 21, 2008 at 02:25:24PM CEST:
> > According to Per Øyvind Karlsen on 4/20/2008 6:01 AM:
> > |>> Oh, I'm mixing up bugzilla entries, I actually meant
> > |>> http://bugs.gentoo.org/show_bug.cgi?id=217976.
> > |>
> > |> thanks, the patch you posted does fix this. i wonder why it doesnt
> > |> fail with 2.61 though since the code in question is the same ...
> > |
> > | The change resulting in this is the following:
> >
> > (http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=ce429ecdc036
> >98025176d3003e113e6e003b429f)
> >
> > Thanks for the details. This commit was made by Ralf, not me, so it
> > gives further argument to the rule of reporting to the bug list rather
> > than a private developer (particularly since I didn't have access to my
> > email over the weekend, leading to this lag in reading your complete
> > thread).
>
> Can we see the complete thread somewhere?
Eric responded to the relevant e-mails. really it was just me asking Per to
send to bug-autoconf ;).
> This bug does not happen with
>
> AC_CONFIG_FILES([foo
> bar])
>
> It can happen with
>
> f='foo
> bar'
> AC_CONFIG_FILES([$f])
>
> or with obsolete:
>
> CONFIG_FILES="foo
> bar" ./config.status
>
> which is not fixed by your patch. So I'd like to see more information
> on how you triggered this issue, maybe I overlooked something, before
> venturing into a fix.
the referenced Gentoo bug (217976) is an example. if the autotool code in
mysql-5.0.56 is rebuilt with <=autoconf-2.61 it works. if vanilla
autoconf-2.62 is used, it fails. if autoconf-2.62 + Per's patch are used, it
works (not suggesting that Per's patch is correct, just that it makes an
obvious difference).
see comment #3 in the bug as for the error output to look for during the mysql
configure process (really the berkdb subdir).
i can try to track it down further for more of a test case than "run
autoreconf && ./configure with mysql-5.0.56", but if you could have a quick
look see first, that would be great as you'll have an idea of what to look
for in the configure.ac files.
-mike
signature.asc
Description: This is a digitally signed message part.