This is the mail archive of the
mailing list for the glibc project.
Re: Changing WCHAR_TYPE from "long int" to "int"?
- To: gcc at gcc dot gnu dot org, GNU C Library <libc-alpha at sourceware dot cygnus dot com>
- Subject: Re: Changing WCHAR_TYPE from "long int" to "int"?
- From: Daniel Jacobowitz <drow at mvista dot com>
- Date: Sun, 5 Aug 2001 14:26:46 -0700
- References: <20010805094806.A3146@lucon.org>
On Sun, Aug 05, 2001 at 09:48:06AM -0700, H . J . Lu wrote:
> I am working with Eric to clean up the Linux/mips configuration in
> gcc 3.x. I'd like to change WCHAR_TYPE from "long int" to "int". They
> are the same on Linux/mips. There won't be any run-time problems. I am
> wondering if there are any compatibility problems at the compile time
> at the source and binary level. For one thing, __WCHAR_TYPE__ will be
> changed from "long int" to "int". The only thing I can think of is
> the C++ libraries. But gcc 3.x doesn't work on Linux/mips. The one
> I am working on will be the first gcc 3.x for Linux/mips. So there
> shouldn't be any problems. Am I right?
What on earth is your definition of "doesn't work"? You apply that
phrase very freely. I have a cross and native compiler, with less than
two dozen lines of patch over GCC 3.0 release, that is capable (despite
everyone's claims) of building glibc and an entire functional Linux/MIPS
distribution, debug info and all. I haven't finished running tests
over it, but the vast majority work perfectly.
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer