X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f X-Recipient: djgpp-workers AT delorie DOT com 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=mf6TmcnUDq2A8qw3aqGKcOu+7soK5aqxvmT3YabBAFI=; b=qQsUkFePUg0u0FoiWUSNSiFgnEWjTbqe35ve9+6bkv7p+YLTLrIy5v5sUM0qTs6y9g 27IjFtsxzNXSX86AZBdav805sS1R9BwIIqVFv53rodPhhKxBusm7IFpGqPu47ztkoxXs 3cfLfrk7N9bOqyrqg35op/f6Ol005NUsCWnhwlYQ+RsUEWjfcVmAsEfqxEgfjz3EZ1ve iMaIz9uxRGIsDRilOgLN0pkbypKHpkaEauLzpusvEQ9+jqWZp3xBSAxSwPLuL42cCKwA zPYxstki8uhzLt86LuZamugb+FeERVlHVTaFvKff8e1NDGXEXcGDezzXPlE7ghuT5MR8 9phg== MIME-Version: 1.0 In-Reply-To: <504F6729.5000505@iki.fi> References: <201209111230 DOT q8BCU0rl001296 AT dexter DOT ludd DOT ltu DOT se> <504F3374 DOT 3080400 AT iki DOT fi> <504F6729 DOT 5000505 AT iki DOT fi> Date: Tue, 11 Sep 2012 23:38:32 -0500 Message-ID: Subject: Re: Invalid tests for __STDC_VERSION__ in DJGPP header files From: Rugxulo To: djgpp-workers AT delorie DOT com Content-Type: text/plain; charset=ISO-8859-1 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 Hi, On Tue, Sep 11, 2012 at 11:30 AM, Andris Pavenis wrote: > > Tried > > --- stdint.h.orig 2012-09-09 19:12:59.000000000 +0300 > +++ stdint.h 2012-09-11 19:19:56.936112793 +0300 > @@ -9,7 +9,7 @@ > #endif > > > #if (defined(__STDC_VERSION__) && __STDC_VERSION__ >= 199901L) \ > - || !defined(__STRICT_ANSI__) > + || !defined(__STRICT_ANSI__) || defined(__cplusplus) > > typedef signed char int_least8_t; > typedef unsigned char uint_least8_t; > > Fixes libstdc++ build problems for gcc-4.8.0 20120909 (again cross-native > build as > after removing libstdc++-v3 build directory 'make -j12' on Intel 3930K > rebuilds it > under Linux in less than 30 seconds) > > The same should be done for other header files which has similar checks. > Does it look OK? Here's my question: isn't GCC being built as C++03 ? If so, then doesn't that standard lack stdint.h ? A quick search shows that GCC "wraps" existing or provides its own stdint.h for targets if none found. http://gcc.gnu.org/ml/gcc/2009-04/msg00000.html So if DJGPP 2.03p2 doesn't have stdint.h, won't it need fixing wherever the GCC-provided one exists?