Date: Wed, 28 Jan 1998 13:17:09 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: andrewc AT rosemail DOT rose DOT hp DOT com
cc: djgpp-workers AT delorie DOT com, Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Subject: Re: iostream concern
In-Reply-To: <199801271809.AA167144573@typhoon.rose.hp.com>
Message-ID: <Pine.SUN.3.91.980128131634.3916J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 27 Jan 1998, Andrew Crabtree wrote:

> I'm not sure if the headers came with the actual libraries of with
> the compiler.

They come with the libg++ distribution.

> But if we are going to accept the header files that gcc configure
> wants us to use then we should fix them.

Is this relevant to the problem with _G_fpos_t?  AFAIK, compiling GCC
doesn't require using the C++ headers.  Or is it?

>  The biggest problem is that gcc uses its own stddef.h which is
> totally incompatible with dj's stdio.h.

If I understand correctly, the problem with stddef.h is another
problem, not directly related to _G_fpos_t, right?

If so, please describe it.  AFAIK, the headers which GCC brings with
it are only for platforms where you need to compile it with the native
compiler which doesn't have ANSI headers such as stddef.h.  This is
not our case, so it shouldn't be a problem.

Robert, can you tell whether you saw this problem when you build GCC,
and if so, how should it be solved?