I couldn't find this in the manual, or with a quick glance through my
list archive: are there any rules about the usage of tabs in configure.in?
I just came across some configure.in code that fails if used with tabs.
Personally, I'd consider it best practice to avoid tabs, but are there
any
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> Do I need a ChangeLog entry when applying the below patch, and
Lars> do I need approval for a TODO-file patch?
No, good ahead.
Lars> +* autoconf.texi +Move the specific macro documentation blocks
Lars> into the source files, and use
> "Lars" == Lars Hecking <[EMAIL PROTECTED]> writes:
Lars> I couldn't find this in the manual, or with a quick glance
Lars> through my list archive: are there any rules about the usage of
Lars> tabs in configure.in? I just came across some configure.in code
Lars> that fails if used with tab
> M4 is insensitive to it, and autoconf.sh does not try to smash them.
> Nonetheless, trailing spaces are smashed.
>
> What problem do you face?
The current version of GNU gettext's m4/gettext.4 contains the following
| [case " "$CONFIG_FILES" " in *" po/Makefile.in "* | *" po/Makefile.in:"*
On Thu, Apr 26, 2001 at 05:34:22PM +0200, Akim Demaille wrote:
: From: Akim Demaille <[EMAIL PROTECTED]>
:
: Basically, my feeling is
:
: 1. 2.15 is a bug fix release only. It should not introduce new
:-D
Lars J
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
> From: Akim Demaille <[EMAIL PROTECTED]>
> :
> : Basically, my feeling is
> :
> : 2.15 is a bug fix release only. It should not introduce new features.
Lars> :-D
:) Indeed :)
| The current version of GNU gettext's m4/gettext.4 contains the following
|
| | [case " "$CONFIG_FILES" " in *" po/Makefile.in "* | *" po/Makefile.in:"*)
| | sed -e "/POTFILES =/r po/POTFILES" po/Makefile.in > po/Makefile
| | ;;
| | esac])
|
|
| compared to
|
| [case "$CONFIG_FI
| | The current version of GNU gettext's m4/gettext.4 contains the following
| |
| | | [case " "$CONFIG_FILES" " in *" po/Makefile.in "* | *" po/Makefile.in:"*)
| | | sed -e "/POTFILES =/r po/POTFILES" po/Makefile.in > po/Makefile
| | | ;;
| | | esac])
| |
| |
| | compared to
| |
> Err, maybe I was not answering on the spaces you were referring to.
>
> If you refer to the spaces in the case argument and in the patterns,
> it's nothing but protection against collisions such as
> topo/Makefile.in. So they want spaces in the patterns, as a
> separator, but then they need
Lars Hecking <[EMAIL PROTECTED]> writes:
> The current version of GNU gettext's m4/gettext.4 contains the following
>
> | [case " "$CONFIG_FILES" " in *" po/Makefile.in "* | *" po/Makefile.in:"*)
> | sed -e "/POTFILES =/r po/POTFILES" po/Makefile.in > po/Makefile
> | ;;
> | esac])
>
| The way it is now, their code is highly fragile, because it presumes
| a particular formatting of AC_OUTPUT. It breaks on
|
| po/Makfile.in.in\n
| \tpo/Makefile.in.in
| \tpo/Makefile.in.in\tfoo/Makefile.in
Yep. Looping is probably the best (after AC_CONFIG_FILES). Or
case " "`echo $CONFI
On Monday 23 April 2001 4:29 pm, Akim Demaille wrote:
> > "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
>
> Alexandre> That's why we should have this portability library coded in
> Alexandre> m4sh. Instead of repeatedly fixing the same problems over
> Alexandre> and over, we should ha
On Tuesday 24 April 2001 8:48 pm, J. Liu wrote:
> Hello,
>
> I am new to autoconf. would please give me soem detail instruction
>
> on how to install the package and m4 package ?
>
> thanks.
$ PATH=/usr/local/bin:$PATH
$ wget ftp://ftp.gnu.org/gnu/m4/m4-1.4.tar.gz
$ wget ftp://ftp.gnu.org/gnu/au
13 matches
Mail list logo
