bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Autoconf 2.56 is released


From: Pavel Roskin
Subject: Re: Autoconf 2.56 is released
Date: Fri, 15 Nov 2002 17:23:46 -0500 (EST)

Hello!

> Back in June, I tried to upgrade LilyPond to 2.53, without success.  I
> sent a bug report
> 
>     http://mail.gnu.org/pipermail/bug-autoconf/2002-June/001658.html
>     
> but didn't hear anything, so I decided to wait.

I have tried Autoconf 2.56 with lilypond 1.7.7.  Just put install-sh,
config.sys and config.sub to the top level directory or add this string to
configure.in:

AC_CONFIG_AUX_DIR(stepmake/bin)

and this to stepmake/configure.in:

AC_CONFIG_AUX_DIR(bin)

Problem solved.  Of course, there may be more things to do.  Perhaps you
should use three-argument form of AC_DEFINE instead of acconfig.h (which
is called config.hh.in in lilypond) - this works even with Autoconf 2.13,
so you can do it as the first step.

You should use m4 quoting (square brackets) instead of shell quotes, 
because Autoconf 2.5x preserves shell quotes.  So this (from aclocal.m4)

AC_MSG_CHECKING("$r version")

should become this:

AC_MSG_CHECKING([$r version])

The problem with lilypond is that it has a lot of custom configuration
code.  It defines LN_S, LN, INSTALL based on the OS name.  It's against
the philosophy of Autoconf, and most importantly, Autoconf also does it,
sometimes in a different way.

However, the configuration system of lilypond is quite simple, compared
to, say, ALSA or Mozilla.  If I was sure that my changes would be applied,
I would fix it within hours.  But I'll appreciate if you do it :-)

Seriously, if maintainers of Lilypond want me to update it to Autoconf
2.56, I'm ready to do it.  It's a great program, and I'll be glad to help
improving it.

-- 
Regards,
Pavel Roskin





reply via email to

[Prev in Thread] Current Thread [Next in Thread]