This is the mail archive of the
mailing list for the GCC project.
Re: Using NLS in the regression checker
- To: pthomas at suse dot de
- Subject: Re: Using NLS in the regression checker
- From: Geoff Keating <geoffk at cygnus dot com>
- Date: Sat, 21 Oct 2000 14:10:04 -0700
- CC: gcc at gcc dot gnu dot org
- References: <20001021193015.A9987@Jeffreys.suse.de>
> Date: Sat, 21 Oct 2000 19:30:15 +0200
> From: Philipp Thomas <firstname.lastname@example.org>
> Cc: email@example.com
> Mail-Followup-To: Geoff Keating <firstname.lastname@example.org>, email@example.com
> Content-Disposition: inline
> User-Agent: Mutt/1.1.11-current-20000402i
> while grumbling over yet another file removed from the source tree but not
> from POTFILES.in, it suddenly dawned on me that it may be possible to
> activate NLS in the regression checker. That way the regression checker
> would catch these cases and the usefullnes of the NLS support wouldn't rely
> on me making regular compiles.
[Aargh! Was that me? Sorry!]
Sure. Just change configure.in so that NLS is switched on by default,
and the regression tester will test it automatically. I'm happy to
add any tools to the regression tester's environment that it might need.
> Note that you don't need the the gettext tools installed in order to check.
> Just do a 'make stamp-check-po' in gcc/po and it'll fail if POTFILES.in
> hasn't been kept up-to-date.
... or add 'make stamp-check-po' to 'make check'.
I don't want to have the regression tester differ greatly from the
normal 'configure && make && make check' build process, because
otherwise it'll be testing something different to what most people
- Geoffrey Keating <firstname.lastname@example.org>