X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A82D5CD.1020604@comcast.net> Date: Wed, 12 Aug 2009 10:46:37 -0400 From: Larry Adams User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Supporting Data Types "ushort_t" and "uchar_t" References: <4A82CBB1.30507@comcast.net> <20090812141530.GA14016@calimero.vinschen.de> <4A82CF78.4050504@comcast.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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