X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Tue, 19 May 2015 18:01:03 +0300
Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and truncated.
From: "Eli Zaretskii (eliz AT gnu DOT org)" <djgpp AT delorie DOT com>
Subject: Re: ANNOUNCE: DJGPP 2.05 beta 1
In-reply-to: <555AADE6.3030905@iki.fi>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <83lhgkehn4.fsf@gnu.org>
References: <201505042003 DOT t44K3odg011007 AT delorie DOT com> <CAA2C=vAjN-HamFRWCQak=QF_NPjR5-TBYZw1U5707MO0b=qXkw AT mail DOT gmail DOT com> <554DF584 DOT 4020309 AT iki DOT fi> <CAA2C=vDaOJb_RW2bQEFoM_cqwp7yhzwX-CB328r5GCCi6XcooA AT mail DOT gmail DOT com> <55501DAD DOT 1080604 AT iki DOT fi> <CAA2C=vAvMW-yquZLSN=Z39NU24Kqf7urjan90801i7BDTdqOvQ AT mail DOT gmail DOT com> <55579278 DOT 8090301 AT iki DOT fi> <CAA2C=vBaQKzmch_buxFm20DJLcG+zv6d6803+qMEx=baA4Frog AT mail DOT gmail DOT com> <555829A6 DOT 8010502 AT iki DOT fi> <CAA2C=vA73qPvoDFytp3FeW6bCD1-XuGsFFoDinoKn2KYY1fkow AT mail DOT gmail DOT com> <555870E8 DOT 7040302 AT iki DOT fi> <CAA2C=vDhD6BJj89o1i0FRd2U0H4bTpGGN4zH6qs7FJKxzqhuQg AT mail DOT gmail DOT com> <201505180114 DOT t4I1EiaX017288 AT envy DOT delorie DOT com> <CAA2C=vCyrQ_+Yq6XsRD-UO4r=j9WoGGiXoqQFrkbiEQpzX+=MA AT mail DOT gmail DOT com> <201505181216 DOT t4ICGaKO014123 AT envy DOT delorie DOT com> <CAA2C=vCk5MY74z+HNVzzdLByg71Y_9ObK-1jPxJ_KF8eqRDZMQ AT mail DOT gmail DOT com> <83zj52dkns DOT fsf AT gnu DOT org>
 <CAA2C=vAPcN+MKC_2tcZqVmo9gvF2Cxdo+K+-qfKaNrQuCkMnEw AT mail DOT gmail DOT com> <555A0DD5 DOT 1010607 AT iki DOT fi> <83r3qdemuj DOT fsf AT gnu DOT org> <555AADE6 DOT 3030905 AT iki DOT f>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Tue, 19 May 2015 06:28:38 +0300
> From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi)" <djgpp AT delorie DOT com>
> 
> >> Including GCC own headers at first is expected behavior.
> > ...that including GCC headers is fine, provided that it's needed.
> GCC includes own headers before DJGPP ones when building user applications. As result
> several DJGPP headers gets overridden by GCC ones for user
> applications.

Sorry, I don't follow.  Are you talking about the situation where
"-nostdinc" is used, like we do in the library build?  If so, I think
only the headers from the explicitly mentioned -I directories are
included, and if so, the order of the directories mentioned on the
command line using -I is what determines which headers are included
first.  Isn't that true?

> I think it is best to have libc build environment as close to one
> used after that by users of built library as possible. We need to
> replace installed DJGPP header ones with ones from version we are
> building for that.

I don't think this is a practical alternative.  There should be a way
of building a library without overriding the production environment.
E.g., what if one wants to build a snapshot, or a version of the
development code that is not yet ready for prime time?  You cannot
tell users to break their production environment.

> > But why is it needed?  Andris, you installed the change that added
> > that 2 years ago; do you remember what was the reason for that?
> Well, we discussed it recently again. Related file (time.h) is now changed not to include GCC own 
> header
> files directly any more.

So this additional inclusion is not needed anymore, I guess.

> I would like however like to leave things as they are for reasons
> mentioned above

I don't yet understand those reasons, so I cannot tell if I agree.

> >> I verified now that for MINGW cross-compiler (I have it installed) "#include_next <float.h>" is at end of GCC float.h.
> > In my native MinGW installation, there's no such include_next, FWIW.
> 
> Fresh download of
> 
> http://garr.dl.sourceforge.net/project/mingw-w64/Toolchains%20targetting%20Win32/Personal%20Builds/dongsheng-daily/4.8/gcc-4.8-win32_4.8.5-20150512.7z
> 
> shows that MINGW GCC float.h has '#include_next <float.h>' at end. Perhaps You have some different 
> older version

I'm using the last official mingw.org distribution of GCC, whcih is of
GCC 4.8.1.