X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Date:	Thu, 31 Jan 2008 19:17:26 -0500
Message-Id:	<200802010017.m110HQEF011717@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:
	<f7dabc25-a683-4f73-a10a-fd33125f4adc AT q77g2000hsh DOT googlegroups DOT com>
	(message from RayeR on Thu, 31 Jan 2008 16:08:21 -0800 (PST))
Subject:	Re: How to determine LIBC version from a GCC toolchain?
References:	<85dee0d5-db2a-4541-809f-1368e5bfa833 AT d70g2000hsb DOT googlegroups DOT com>
	<200801312257 DOT m0VMvA9B009573 AT envy DOT delorie DOT com> <f7dabc25-a683-4f73-a10a-fd33125f4adc AT q77g2000hsh DOT googlegroups DOT com>
Errors-To:	nobody AT delorie DOT com

> > It's in include/sys/version.h
> 
> There I have 2.4 but mingw and arm-gcc doesn't have such header.

Like I said, they each use different C libraries, so you CAN'T COMPARE
VERSION NUMBERS.  They're not just different versions of the same
library, they're completely different libraries.

> I'm trying to understand why format string %hhu in sscanf works wrong
> (behaves same as %hu) in arm-gcc but same code works fine in djgpp and
> ming32. So I think it have something to do with libc and maybe arm-gcc
> 3.4.6 uses some older library which didn't supported %hhu or it may be
> bug specific to arm port. I don't know

You'll have to ask the arm-gcc port people, not the djgpp people.

- Raw text -