Mail Archives: cygwin/2002/06/01/14:29:28
--------------BD06CAB082AF33224B03847D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
It doesn't properly report i586 CPU. I haven't had a round tuit moment
to look into it myself. Instead of i586 you get i686.
Earnie.
--------------BD06CAB082AF33224B03847D
Content-Type: message/rfc822;
name="cygwin.51148"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="cygwin.51148"
Date: Fri, 31 May 2002 22:55:55 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: try try again (waiting for the retraction/correction)
Message-ID: <20020601025555 DOT GA29537 AT redhat DOT com>
Reply-To: cygwin AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
On Tue, May 28, 2002 at 09:10:52PM +0000, perlspinr AT att DOT net wrote:
>I need proper information for makefiles to get, and I *am* using uname
>to get that info. It's wrong too (I am NOT at that system this pm and
>cannot double-triple- check that, but am very close to sure, and if I
>was wrong I'll post a retraction/correction about it later, when I've
>had a chance to re-check it, if I am not banned from the List by then).
Well, you're not banned from the list (I don't ban people for blowing
off steam).
Since I'm going to be releasing 1.3.11 soon, I'm interested in knowing
of potential problems with uname.
If you could provide a summary of what's wrong with uname, I'll try to
fix it before the next release.
If this was just cockpit error, it would be useful to know that too,
since you are so adamant about claiming that uname is wrong.
cgf
--------------BD06CAB082AF33224B03847D
Content-Type: text/plain; charset=us-ascii
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--------------BD06CAB082AF33224B03847D--
- Raw text -