This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: try try again


On Tue, May 28, 2002 at 08:18:00PM +0000, perlspinr@att.net wrote:
>Still hoping that someone will find this important enough to answer.
>
>An updated detail is that I can override the value of "MACHTYPE" and
>"HOSTTYPE" in Cygwin per se, but not in MSYS -- Earnie?  CC:ing you
>this time.

Again, this is *not* an Msys mailing list.  I find the concept of a
cygwin fork annoying enough without having to see discussion of it here.

If you have msys questions seek elsewhere.

As to why it isn't i586 on your Pentium, after a cursory glance at the
source (gasp!), it's obviously because this was the configuration
triplet used to build bash.  Performing complicated "what type of cpu is
this?" checks is really not something I'd want my shell to spend time
on.  So bash apaprently wisely just provides information based on whatever
it was built for.

If you need better information, use uname.

cgf

>From:    perlspinr@att.net
>To:      cygwin@cygwin.com
>Subject: A small question on machine id
>Date:    Sun, 26 May 2002 19:13:20 +0000
>
>The formal architecture triplet like:
>cpu-company-os(-kernel)
>
>on my Pentium machine gives
>MACHTYPE=i686-pc-cygwin
>and it's the same in Earnie's current Msys cygwin DLL -
>based system as in Cygwin proper.
>
>I am wondering why?
>
>Obviously one would expect the shell variable value to be
>"i586-pc-(cygwin|msys)"?

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]