X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Thu, 04 Apr 2013 06:00:03 +0300
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: snprintf not found
In-reply-to: <515CB460.9030509@usc.edu>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <83zjxff1ak.fsf@gnu.org>
References: <515B8EE7 DOT 4060603 AT usc DOT edu> <83ehesib96 DOT fsf AT gnu DOT org> <515CB460 DOT 9030509 AT usc DOT edu>
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: Wed, 03 Apr 2013 14:59:44 -0800
> From: Mikhail Ryazanov <ryazanov AT usc DOT edu>
> 
> Thanks for the explanation!
> I have v2.03, as zip-picker suggested. How usable is v2.04 now?

I don't know, sorry.

> >> P.S. For comparison, gcc 4.6.1 in Debian works fine.
> > GCC version has nothing to do with this.  Standard functions are
> > implemented in the library, not in the compiler.
> 
> I understand, but they must be not only implemented in the library, but 
> also declared in library header files, which in turn have some 
> correlation with the compiler. At least, "4.72" in the path
> 
> DJGPP/include/cxx/4.72/cstdio
> 
> suspiciously resembles "4.7.2" in the output of
> "DJGPP/bin/gcc.exe --version". ;-)

That's because this particular header is part of the GCC distribution.

> So, back to v2.03/v2.04. Currently the problem in C++ occurs even before 
> that linker cannot find snprintf in the library -- the compiler simply 
> does not see its declaration. If I replace djdev203 with djdev204, will 
> it start seeing? Or I need to update gpp as well?

The library and the headers are consistent, so it's not a surprise
that the compiler whines when it sees the headers.

Theoretically, upgrading to v2.04 should solve this, and I don't think
you will need to replace the compiler.