Message-Id: <200006201802.VAA18292@alpha.netvision.net.il> Date: Tue, 20 Jun 2000 21:05:13 +0200 X-Mailer: Emacs 20.6 (via feedmail 8.1.emacs20_6 I) and Blat ver 1.8.5b From: "Eli Zaretskii" To: Laurynas Biveinis CC: djgpp-workers AT delorie DOT com In-reply-to: <394E8249.1E993FEC@softhome.net> (message from Laurynas Biveinis on Mon, 19 Jun 2000 22:27:53 +0200) Subject: Re: Patch: sentinels for typedefs in headers (long) References: <200006141013 DOT MAA19472 AT lws256 DOT lu DOT erisoft DOT se> <394E8249 DOT 1E993FEC AT softhome DOT net> 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 > Date: Mon, 19 Jun 2000 22:27:53 +0200 > From: Laurynas Biveinis > > I have written the following. Thanks! > Also, it is OK for me to write on the behalf of all of you? It's fine with me. > Currently we see following possible solutions: > 1) Override USER_H and not install those headers for DJGPP. > However, discussion between FreeBSD maintainers and you showed > that you're not going to accept this solution, although we > were unable to find any _technical_ arguments for doing so. From our discussion here it seems that this is the solution most of us prefer. It is also how DJGPP worked from day one: GCC headers were not installed. So perhaps it is better to limit the message just to this one possibility, and ask the maintainers why, technically, do they insist on installing headers that can potentially conflict with the library internals. It looks like nobody quite understands the technical reasons for this invasive behavior, at least on this forum.