This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: linux libio status
- To: Joe Buck <jbuck at synopsys dot com>
- Subject: Re: linux libio status
- From: Richard Henderson <rth at cygnus dot com>
- Date: Wed, 15 Oct 1997 11:11:27 -0700
- Cc: Jason Merrill <jason at cygnus dot com>, egcs at cygnus dot com
- References: <u97mbfs88f.fsf@yorick.cygnus.com> <199710151551.IAA22184@atrus.synopsys.com>
- Reply-To: Richard Henderson <rth at cygnus dot com>
On Wed, Oct 15, 1997 at 08:51:29AM -0700, Joe Buck wrote:
> The only other alternatives I can think of is to force a #define NULL 0,
> or do some kind of mini-fixincludes on the existing libio.h header.
> (The latter technique could solve the problems with the new lock functions
> as well).
The problem with the fixincludes option is that I ran into the same
problem on RH Linux Alpha not because of <libio.h>, but one of the
kernel header files.
If we leave NULL in the installed C++ headers, redefining NULL is
the only successful option. Which means in my mind: get it out.
r~