X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=hJw69SkJfZX+9nMvLWRpPgBv/PztHrp7534OXYGMdS8=;
        b=XW1A5H0DZq1ZY7Y7hkfG4f3lWfGi5fiF+x6W13z4PWEOjfY3TRSnl+msNbXh8NXoV8
         T8yrr4E3Yflej6BF4oJMRAxMfvs1er88rWPDzRZoPJs2PIqZbjReQ6Y21mDHveC41hI+
         akzN8Cij4/WZiRH+fe72vouvUd8zCJ8N2tLCxeud/XuwW1dl8G7HIjhIKDkb8xlXMaF9
         GYjpYRm2Q7f7R5znFtKW2x2ESV6z2fN9CHsqTjDq37A9kbNqtV0UyHaN4DxwEgprVfXS
         J+9CM2jvUiyFEO0Z39T264Q5j7PVNyA5Yf6TfvhvEth8+CaVcnSxGRfr15x+JvwGtAV1
         Hhkg==
MIME-Version: 1.0
X-Received: by 10.50.66.172 with SMTP id g12mr15500551igt.34.1431965592165;
 Mon, 18 May 2015 09:13:12 -0700 (PDT)
In-Reply-To: <83wq05eukk.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>
	<83wq05eukk DOT fsf AT gnu DOT org>
Date: Mon, 18 May 2015 19:13:12 +0300
Message-ID: <CAA2C=vBKihqvw152LsGvWEiSei7TczN6Vmxsvebtnoz_E5=u4g@mail.gmail.com>
Subject: Re: ANNOUNCE: DJGPP 2.05 beta 1
From: "Ozkan Sezer (sezeroz AT gmail DOT com)" <djgpp AT delorie DOT com>
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
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

On 5/18/15, Eli Zaretskii (eliz AT gnu DOT org) <djgpp AT delorie DOT com> wrote:
>> Date: Mon, 18 May 2015 18:22:35 +0300
>> From: "Ozkan Sezer (sezeroz AT gmail DOT com)" <djgpp AT delorie DOT com>
>>
>> --- makefile.inc	30 Apr 2015 18:50:42 -0000	1.16
>> +++ makefile.inc	18 May 2015 15:15:30 -0000
>> @@ -51,7 +51,7 @@
>>
>>  # Find GCC own include directory and add it to CFLAGS
>>  GCC_INC_DIR := $(shell $(CROSS_GCC) -print-file-name=include)
>> -CFLAGS += -I$(GCC_INC_DIR)
>> +#CFLAGS += -I$(GCC_INC_DIR)
>>
>>  # Pass defines as compiler/assembler switches
>>  CFLAGS += -DGAS_MAJOR=$(GAS_MAJOR)
>>
>> Now do a make clean, recompile and compare the old and new strtod.d:
>>
>> --- 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?