Supporting Data Types "ushort_t" and "uchar_t"

Wed Aug 12 14:47:00 GMT 2009

Mark,
It compiles fine on Solaris 10 right now using the two typdef's. 
However, not in Cygwin. I am presently checking if this is also new to 
RHEL4/5, SUSE10.2, and FreeBSD. I suspect somewhat similar results. 
Since the code is ours (The Cacti Group), I can still continue to use 
"unsigned short int" and "unsigned char" without issues (and I assume 
Solaris 10 too). My concern is that the "*_t" typedefs are supposed to 
be hardware architecture agnostic, and there must have been some reason, 
other than "geeze everything else is that way, so why not do those two" 
to have done this for Solaris.
Larry
Mark J. Reed wrote:
> On Wed, Aug 12, 2009 at 10:19 AM, Larry Adams wrote:
>>> It's Solaris 10 :(. They must "set" the standard these days ;)
>>>> Hm. How did Solaris 10 typedefs show up? Does the app in question not
> compile out of the box on Linux, either?
>>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple