Message-ID:	<393E415C.9E557849@softhome.net>
Date:	Wed, 07 Jun 2000 15:34:36 +0300
From:	Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer:	Mozilla 4.72 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	"Martin v. Loewis" <martin AT loewis DOT home DOT cs DOT tu-berlin DOT de>
CC:	gcc AT gcc DOT gnu DOT org, djgpp-workers AT delorie DOT com
Subject:	Re: GCC and system headers
References:	<393D3934 DOT 8AB76C44 AT softhome DOT net> <200006062113 DOT XAA01561 AT loewis DOT home DOT cs DOT tu-berlin DOT de>
Reply-To:	djgpp-workers AT delorie DOT com

"Martin v. Loewis" wrote:
> 
> > could somebody explain what are the technical reasons for
> > not allowing ports to choose if they want to use standard
> > headers provided by GCC? Many times I've seen on this
> > mailing list that 'overriding USER_H is a brain-damaged
> > feature' without explanation *how* it is brain-damaged.
> 
> Please elaborate; I'm not aware of any prior discussion of this topic.

See e.g. http://gcc.gnu.org/ml/gcc/1999-09n/msg00827.html and other
messages in this thread.

> What exactly is user.h, and what does it have to do with ports? 

USER_H variable defined in gcc/Makefile. It specifies which GCC
provided headers should be installed on system. Ports could
override it in target makefile fragments.

> And
> who said that they must not choose whether they want to use standard
> headers?

Jeff Law said that many times in the thread mentioned above.

Laurynas Biveinis

- Raw text -