Mail Archives: cygwin/2001/11/16/11:40:58
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 DOT steinmann AT insonic DOT com]
Sent: Friday, November 16, 2001 6:46 AM
To: cygwin AT cygwin DOT 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 DOT steinmann AT insonic DOT 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/
- Raw text -