www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1998/02/02/19:59:00

From: Andrew Crabtree <andrewc AT typhoon DOT rose DOT hp DOT com>
Message-Id: <199802030057.AA212517422@typhoon.rose.hp.com>
Subject: Re: iostream concern
To: dj AT delorie DOT com (DJ Delorie)
Date: Mon, 02 Feb 1998 16:57:02 PST
Cc: andrewc AT rosemail DOT rose DOT hp DOT com, djgpp-workers AT delorie DOT com
In-Reply-To: <199802030042.TAA22344@delorie.com>; from "DJ Delorie" at Feb 2, 98 7:42 pm
Reply-To: andrewc AT rosemail DOT rose DOT hp DOT com

>  What's in gnu's stddef.h that djgpp's been
> missing all these years?
Presumably absolutely nothing.  Thats not my concern.  Its just that
currently, anyone attempting to build a unix->djgpp compiler, or
attempting to bootstrap a compiler from unix, is going to have the
make process abort with 

/usr/local/lib/gcc-lib/i586-go32-msdos/pgcc-2.90.23/include/stdio.h:36: warning:
 redefinition of `size_t'
/tmp/gnu/egcs-1.0.1/gcc/ginclude/stddef.h:168: warning: `size_t' previously decl
ared here

And they will have to know that the must re-extract stddef.h from the 
dj cross kit and overwrite the gnu.  I'm just annoyed because I haven't figured
out how to disable gcc from using its own stddef.h in the build process, and thought
that moving size_t into stddef.h might be a decent alternative since (for 
people really concerned with standards compliance) it should be there anyway.

Andy




- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019