This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: i18n changes
- To: Richard Henderson <rth at cygnus dot com>
- Subject: Re: i18n changes
- From: Philipp Thomas <pthomas at suse dot de>
- Date: Wed, 31 May 2000 04:36:06 +0200
- Cc: gcc-patches at gcc dot gnu dot org, Mark Mitchell <mark at codesourcery dot com>,Zack Weinberg <zack at wolery dot cumb dot org>
- References: <20000530214036.S12004@Jeffreys.suse.de> <20000530141129.B14163@cygnus.com>
* Richard Henderson (rth@cygnus.com) [20000530 23:12]:
> On Tue, May 30, 2000 at 09:40:36PM +0200, Philipp Thomas wrote:
> > - enable NLS by default when not building a cross compiler.
>
> More correctly, when not building a canadian cross compiler.
> I.e. enable nls whenever build == host.
# if cross compiling, disable NLS support.
# It's not worth the trouble, at least for now.
if test "${build}" != "${host}" -o \
"${build}" != "${target}" -o \
"${host}" != "${target}"
As you can see from this fragment, it's also disabled for host != target, so
it's not only building a canadian cross compiler that would disable nls.
Would that be correct? Or should really only canadian cross be a reason to
disable it?
I just don't have any experience with any kind of cross compiler, so I'm
rather unsure of what the implications/requirements would be.
Philipp
--
Philipp Thomas <pthomas@suse.de>
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany
#define NINODE 50 /* number of in core inodes */
#define NPROC 30 /* max number of processes */
-- Version 7 UNIX fuer PDP 11, /usr/include/sys/param.h