X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Mon, 18 May 2015 20:22:57 +0300 From: "Eli Zaretskii (eliz AT gnu DOT org)" Subject: Re: ANNOUNCE: DJGPP 2.05 beta 1 In-reply-to: X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <83siater66.fsf@gnu.org> References: <201505042003 DOT t44K3odg011007 AT delorie DOT com> <554DF584 DOT 4020309 AT iki DOT fi> <55501DAD DOT 1080604 AT iki DOT fi> <55579278 DOT 8090301 AT iki DOT fi> <555829A6 DOT 8010502 AT iki DOT fi> <555870E8 DOT 7040302 AT iki DOT fi> <201505180114 DOT t4I1EiaX017288 AT envy DOT delorie DOT com> <201505181216 DOT t4ICGaKO014123 AT envy DOT delorie DOT com> <83zj52dkns DOT fsf AT gnu DOT org> <83wq05eukk DOT fsf AT gnu DOT org> <83twv9espx DOT fsf AT gnu DOT org> 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: Mon, 18 May 2015 19:59:05 +0300 > From: "Ozkan Sezer (sezeroz AT gmail DOT com)" > > On 5/18/15, Eli Zaretskii (eliz AT gnu DOT org) wrote: > >> Date: Mon, 18 May 2015 19:13:12 +0300 > >> From: "Ozkan Sezer (sezeroz AT gmail DOT com)" > >> > >> >> --- strtod.d.bak > >> >> +++ strtod.d > >> >> @@ -1,7 +1,6 @@ > >> >> strtod.o: strtod.c ../../../../include/libc/stubs.h \ > >> >> ../../../../include/locale.h ../../../../include/math.h \ > >> >> ../../../../include/stdlib.h ../../../../include/sys/djtypes.h \ > >> >> - > >> >> /usr/local/cross-djgpp/lib/gcc/i586-pc-msdosdjgpp/3.4.6/include/float.h > >> >> \ > >> >> ../../../../include/float.h ../../../../include/errno.h \ > >> >> ../../../../include/ctype.h ../../../../include/inlines/ctype.ha \ > >> >> ../../../../include/inlines/ctype.hp \ > >> >> > >> >> As you see, -nostdinc does prevent compiler's own headers from being > >> >> used. But with current cvs as it is, we are telling the compiler to > >> >> do use its own headers: Not a good idea IMO. > >> > > >> > Are you sure the compiler doesn't use that header when it sees > >> > "-nostdinc"? Could it be that it just doesn't put that header into > >> > the dependencies? > >> > > >> > >> Joke, right? > > > > You mean, you are joking by asking whether I am? > > This is ridiculous. Why "ridiculous"? You asked questions, so I'm trying to help you figure things out. You can ignore what I say if you think it's irrelevant, or doesn't help you. But this reaction of yours is just plain rude, for no good reason (and not for the first time, either). I'm trying to help you as best I can, I don't think I deserve this attitude of yours, even if what I say sound preposterous to you. > Did you even try to reproduce what I said? Did you even care to ask if I can set that up, or have enough time to do so? Why should that be a prerequisite for trying to think aloud about the problem _you_ are asking questions about? Or if that _is_ a prerequisite, please say so loud and clear, and I won't bother answering you if I cannot try it myself. > If you ever bother to do so, you can even add -save-temps to the > cflags and compare the assembler outputs to see what I am saying. I believe you. I didn't ask that question because I thought you were lying, or didn't know what you were talking about. I asked it because these issues are complicated, and sometimes we tend to think we understand something, when in fact we miss some subtle aspects. Like in that example with _open and O_BINARY a couple of days ago. So please don't assume that every question like that is a challenge of your integrity or a personal attack on your intelligence. It's just a normal way of discussing a complicated issue, about which _you_ asked questions. I'm not attacking you, I'm trying to help, goddamit!