RE: bash-2.05a-1: OSTYPE is empty

RE: bash-2.05a-1: OSTYPE is empty

[Troy Noble]

Instead you can safely use the following across platforms (works on Unix in
other words):

case `uname` in
   CYGWIN*) # cygwin-specific stuff here such as OSTYPE=cygwin ;->
            ;;
         *) # non-cygwin stuff here
            ;;
esac

To ease maintainability, be sure not to use CYGWIN_NT* or
CYGWIN_NT-5* if possible.  Or has that been changed now?  I
remember talk of it on the list a couple months back.

I suspect others are going to experience the same Makefile and
shell script breakage if they were relying on OSTYPE & friends.
The uname thing is more stable since it doesn't rely on any
feature of bash per se.

Troy

-----Original Message-----
From: Daniel Steinmann [mailto:daniel.steinmann@insonic.com]
Sent: Friday, November 16, 2001 6:46 AM
To: cygwin@cygwin.com
Subject: Re: bash-2.05a-1: OSTYPE is empty



Corinna Vinschen wrote:
> However, the following is given in the ChangeLog:
> 
> x.  Bash no longer auto-exports HOSTNAME, HOSTTYPE, MACHTYPE, or OSTYPE,
>     even if it assigns them default values.

Obviously I did not read the bash ChangeLog, sorry. 

Now it is clear why in my Makefile the check for OSTYPE does not
work anymore. 

Thank you for your help,
Daniel.

-- 
Daniel Steinmann, Insonic AG, Zuerich, Switzerland
daniel.steinmann@insonic.com, +41 1 456 50 00, fax: +41 1 456 50 01

--
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/

--
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/

bash-2.05a-1: OSTYPE is empty

[Daniel Steinmann]

Today I upgraded to bash-2.05a-1 and noticed that the variable
OSTYPE is empty. Other variables like OS are still ok. So I rolled
back to bash-2.05-8; in this version I get the expected value
'cygwin'.

Is this just my machine (Win2k prof, cygwin-1.3.5) or has anybody
else noticed the same problem?

Daniel.

-- 
Daniel Steinmann, Insonic AG, Zuerich, Switzerland
daniel.steinmann@insonic.com, +41 1 456 50 00, fax: +41 1 456 50 01

--
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/

Re: bash-2.05a-1: OSTYPE is empty

[Daniel Steinmann]

Corinna Vinschen wrote:
> However, the following is given in the ChangeLog:
> 
> x.  Bash no longer auto-exports HOSTNAME, HOSTTYPE, MACHTYPE, or OSTYPE,
>     even if it assigns them default values.

Obviously I did not read the bash ChangeLog, sorry. 

Now it is clear why in my Makefile the check for OSTYPE does not
work anymore. 

Thank you for your help,
Daniel.

-- 
Daniel Steinmann, Insonic AG, Zuerich, Switzerland
daniel.steinmann@insonic.com, +41 1 456 50 00, fax: +41 1 456 50 01

--
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/

Re: bash-2.05a-1: OSTYPE is empty

[Corinna Vinschen]

On Fri, Nov 16, 2001 at 02:13:32PM +0100, Mader, Alexander wrote:
> Daniel Steinmann wrote:
> 
> > Today I upgraded to bash-2.05a-1 and noticed that the variable
> > OSTYPE is empty. Other variables like OS are still ok. So I rolled
> > back to bash-2.05-8; in this version I get the expected value
> > 'cygwin'.
> > 
> > Is this just my machine (Win2k prof, cygwin-1.3.5) or has anybody
> > else noticed the same problem?
> > 
> > Daniel.
> > 
> > 
> 
> Hallo Daniel,
> 
> it seems okay with my machine (NT, todays Cygwin), see below.

However, the following is given in the ChangeLog:

x.  Bash no longer auto-exports HOSTNAME, HOSTTYPE, MACHTYPE, or OSTYPE,
    even if it assigns them default values.

Try

	set | grep OS

and these variables are still available, just not exported.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

Re: bash-2.05a-1: OSTYPE is empty

[Mader, Alexander]

Daniel Steinmann wrote:

> Today I upgraded to bash-2.05a-1 and noticed that the variable
> OSTYPE is empty. Other variables like OS are still ok. So I rolled
> back to bash-2.05-8; in this version I get the expected value
> 'cygwin'.
> 
> Is this just my machine (Win2k prof, cygwin-1.3.5) or has anybody
> else noticed the same problem?
> 
> Daniel.
> 
> 

Hallo Daniel,

it seems okay with my machine (NT, todays Cygwin), see below.

Best regards,

Alexander.


$ set|grep OS
HOSTNAME=L905
HOSTTYPE=i686
OS=Windows_NT
OS2LIBPATH='C:\WINNT\system32\os2\dll;'
OSTYPE=cygwin

$ set|grep BASH
BASH=/usr/bin/bash
BASH_VERSINFO=([0]="2" [1]="05a" [2]="0" [3]="1" [4]="release" 
[5]="i686-pc-cygwin")
BASH_VERSION='2.05a.0(1)-release'

-- 
Alexander Mader <alexander.mader@niles.de>	Fon: +49-30-93033-636
NILES Werkzeugmaschinen GmbH			Fax: +49-30-93033-603
				www.niles.de



--
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/