Date: Wed, 19 Jul 2000 14:27:56 -0400 (EDT)
Message-Id: <200007191827.OAA08699@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: jbuck AT racerx DOT synopsys DOT com
CC: lauras AT softhome DOT net, djgpp-workers AT delorie DOT com,
        martin AT loewis DOT home DOT cs DOT tu-berlin DOT de, gcc AT gcc DOT gnu DOT org
In-reply-to: <200007191524.IAA29726@racerx.synopsys.com> (message from Joe
	Buck on Wed, 19 Jul 2000 08:24:23 -0700 (PDT))
Subject: Re: GCC headers and DJGPP port
References:  <200007191524 DOT IAA29726 AT racerx DOT synopsys DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: Joe Buck <jbuck AT racerx DOT synopsys DOT com>
> Date: Wed, 19 Jul 2000 08:24:23 -0700 (PDT)
> 
> Wouldn't it break the SunOS4 port, or other ports where we're
> bootstrapping from an ancient K&R environment and the C library
> is highly nonstandard?

If the system is probed at configure time for headers, as Mike
suggested, we could arrange for the headers to be installed on such
systems.  Would this be an okay solution?