* Re: $OSTYPE - Aaaaaaaaaaaaaaargh !
@ 2000-05-31 9:20 Earnie Boyd
0 siblings, 0 replies; 4+ messages in thread
From: Earnie Boyd @ 2000-05-31 9:20 UTC (permalink / raw)
To: Michael Ring, cygwin
--- Michael Ring <Michael.Ring@t-mobil.de> wrote:
> On Wed, 31 May 00 14:00:08 +0100, you wrote:
>
> >Hello,
> >
> >with the lastest version of the bash the content of $OSTYPE has changed from
> "cygwin" to "cygwin32" again without further notice. Since I used this entry
> to
> detect the old B20.1 from the new Cygnus V1.1 I have now a lot of broken
> scripts
> and makefiles that have to run on both versions. This drives me really crazy!
> >
>
> It seems that this version of bash was compiled with the config.guess file
> included in the bash distribution. This config.guess stills responds with
> i686-pc-cygwin32
>
Yep.
>
> >So is there any *reliable* method to detect the version of Cygwin from a
> script
> ?
>
> use uname; using bash is a bad idea because bash burns in the values it found
> on
> the host it was built.
>
> Here's how to get the information:
>
> uname
> returns CYGWIN_NT-4.0 or CYGWIN_NT-5.0 (don't know what it returns on
> win95/98
use the source to find out.
> uname -r
> returns 1.1.2s(0.21/2/2) ore simmilar. everything before ( is the version
> number; s seems to mean snapshot)
The 's' was added very recently to mean snapshot.
> uname -m
> returns i686
>
> or, you could distribute config.guess with your script, it returns
> i686-pc-cygwin
> a good place to find config.guess is libtool-1.3.5.tar.gz on ftp.gnu.org
>
No. The best place to get config.guess and config.sub is from the config
directory found at ftp.gnu.org or a mirror.
=====
---
Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
__Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
__Minimalist GNU for Windows__
Mingw32 List: < http://www.egroups.com/group/mingw32/ >
Mingw Home: < http://www.mingw.org/ >
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: $OSTYPE - Aaaaaaaaaaaaaaargh !
@ 2000-05-31 5:53 Michael Ring
0 siblings, 0 replies; 4+ messages in thread
From: Michael Ring @ 2000-05-31 5:53 UTC (permalink / raw)
To: cygwin
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On Wed, 31 May 00 14:00:08 +0100, you wrote:
>Hello,
>
>with the lastest version of the bash the content of $OSTYPE has changed from
"cygwin" to "cygwin32" again without further notice. Since I used this entry to
detect the old B20.1 from the new Cygnus V1.1 I have now a lot of broken scripts
and makefiles that have to run on both versions. This drives me really crazy!
>
It seems that this version of bash was compiled with the config.guess file
included in the bash distribution. This config.guess stills responds with
i686-pc-cygwin32
>So is there any *reliable* method to detect the version of Cygwin from a script
?
use uname; using bash is a bad idea because bash burns in the values it found on
the host it was built.
Here's how to get the information:
uname
returns CYGWIN_NT-4.0 or CYGWIN_NT-5.0 (don't know what it returns on
win95/98
uname -r
returns 1.1.2s(0.21/2/2) ore simmilar. everything before ( is the version
number; s seems to mean snapshot)
uname -m
returns i686
or, you could distribute config.guess with your script, it returns
i686-pc-cygwin
a good place to find config.guess is libtool-1.3.5.tar.gz on ftp.gnu.org
>
>Greetings,
>Jörg
Hope that helps,
Micjael Ring
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: $OSTYPE - Aaaaaaaaaaaaaaargh !
2000-05-31 4:00 jorg.schaible
@ 2000-05-31 5:14 ` Corinna Vinschen
0 siblings, 0 replies; 4+ messages in thread
From: Corinna Vinschen @ 2000-05-31 5:14 UTC (permalink / raw)
To: jorg.schaible; +Cc: cygwin
jorg.schaible@db.com wrote:
>
> Hello,
>
> with the lastest version of the bash the content of $OSTYPE has changed from "cygwin" to "cygwin32" again without further notice. Since I used this entry to detect the old B20.1 from the new Cygnus V1.1 I have now a lot of broken scripts and makefiles that have to run on both versions. This drives me really crazy!
>
> So is there any *reliable* method to detect the version of Cygwin from a script ?
uname -r
Corinna
--
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* $OSTYPE - Aaaaaaaaaaaaaaargh !
@ 2000-05-31 4:00 jorg.schaible
2000-05-31 5:14 ` Corinna Vinschen
0 siblings, 1 reply; 4+ messages in thread
From: jorg.schaible @ 2000-05-31 4:00 UTC (permalink / raw)
To: cygwin
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Hello,
with the lastest version of the bash the content of $OSTYPE has changed from "cygwin" to "cygwin32" again without further notice. Since I used this entry to detect the old B20.1 from the new Cygnus V1.1 I have now a lot of broken scripts and makefiles that have to run on both versions. This drives me really crazy!
So is there any *reliable* method to detect the version of Cygwin from a script ?
Greetings,
Jörg
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-05-31 9:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-05-31 9:20 $OSTYPE - Aaaaaaaaaaaaaaargh ! Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
2000-05-31 5:53 Michael Ring
2000-05-31 4:00 jorg.schaible
2000-05-31 5:14 ` Corinna Vinschen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).