This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Output of "uname -s" and "uname -o"
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 9 Jun 2008 15:24:58 +0200
- Subject: Re: Output of "uname -s" and "uname -o"
- References: <Pine.GSO.4.63.0806042340070.12128@access1.cims.nyu.edu>
- Reply-to: cygwin-developers at cygwin dot com
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.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat