Output of "uname -s" and "uname -o"

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Mon Jun 9 13:44:00 GMT 2008


On Mon, Jun 09, 2008 at 03:24:58PM +0200, Corinna Vinschen wrote:
>On Jun  5 00:07, Igor Peshansky wrote:
>> Hi,
>> 
>> I know this came up before[1], but I don't think this was ever adequately
>> resolved (unless you consider "the thread died down so let's stop worrying
>> about it" an adequate resolution).  Also, while that thread listed some
>> reasons to change the output of uname, it did not really list reasons not
>> to, other than to preserve the status quo.
>> 
>> In my current situation, I'm trying to fix a GNU Makefile that works
>> across Linux and AIX to also work on Cygwin.  The top of the Makefile
>> contains the following: "include $(TOP)/config/Make.$(shell uname -s)".
>> The config directory contains Make.Linux and Make.AIX.
>> 
>> Of course, with the current uname output, make goes to look for
>> config/Make.CYGWIN_NT-5.1 (on my machine).  This is no longer the case of
>> pattern matching, as in the previous thread.  The output of "uname -o" is
>> a nice generic "Cygwin", but on Linux it returns "GNU/Linux" (obviously
>> problematic), and uname on AIX doesn't even recognize "-o".
>
>I don't think we can change this.  The sysname field is the only one
>which you can use to identify the system.  There's no other room for
>this.

That plus the uname has had this format for many years.  It isn't just a
couple of applications that could break if this was changed.

cgf



More information about the Cygwin-developers mailing list