X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <515FC1D2.4000807@iki.fi>
Date: Sat, 06 Apr 2013 09:33:54 +0300
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: snprintf not found
References: <515B8EE7 DOT 4060603 AT usc DOT edu> <83ehesib96 DOT fsf AT gnu DOT org> <2a00b67d-272c-4374-8e00-7d565f9c37e4 AT googlegroups DOT com> <515F7143 DOT 7010706 AT usc DOT edu>
In-Reply-To: <515F7143.7010706@usc.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

On 04/06/2013 03:50 AM, Mikhail Ryazanov wrote:
>
> However, I use DJGPP mostly as a mean to run gcc under MSW for checking standard compliance and
> portability, so the idea is that it must compile my sources without tweaking them. :-)

About standard compliance. If You take a look at:

http://gcc.gnu.org/projects/cxx0x.html
http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.200x

You'll see references to standard issues that cannot be supported for DJGPP (like all thread
related stuff). The related stuff has not been removed from libstdc++-v3 for DJGPP port but
it will just not work or likely even not compile.

> Do you know about any problems with v2.04?

I would suggest to search mailing list archives for that.

Also:

Standards compliance was one of the reasons why DJGPP port of gcc-4.8.0 is supported for
DJGPP v2.04 development versions only (not v2.03 any more): missing C library functions
caused libstdc++-v3 features to be disabled for DJGPP v2.03. I did not build for v2.03
either.