What's in a name?
Thu Nov 30 15:24:00 GMT 2000
On Thu, Nov 30, 2000 at 06:09:42PM -0500, David A. Cobb wrote:
>> >At 02:58 PM 11/30/2000, David A. Cobb wrote:
>> >>That's nice, I thought, because I need to key a load of directory
>> >>references depending on whether I'm in Win32 or Cygwin. HOWEVER,
>> >>several installations seem to think it should be "-Cygwin32" when they
>> >>build their "/usr/local/???/i686-pc-?????????" subtrees.
>> >These are old. Cygwin used to be referred to as Cygwin32.
>So, Question#1 would be: where does bash get the initial value?
Don't know. I assume from whatever is used when it is configured.
>> >>And 'config.guess', at least the one I looked at calls 'uname' which
>> >>says I have an
>> >>"i586" and cannot make any sense out of my configuration at all.
>> >Interesting. Mine says:
>> > >uname -m
>> >Are you sure you're up-to-date in your Cygwin environment?
>> Cygwin should accurately depict the machine type. If you're using
>> a '586' it should report that fact.
>> It depends on Windows for this information. uname.cc has the gory
>So, what's an "Intel Celeron @ 466 MHz" which is all I see on the box.
We rely on whatever Windows says it is. There is no magic code here.
Windows returns a processor type via the GetSystemInfo function and that
is what we use.
>And, while we're on the subject, I see that bash also thinks I logged
>on as "Administrator" which leads to another mailgram. [later] I know,
>I know, grap the sources of `uname' and look :-)
While we're on the subject, you might want to look up the word
"Administrator" in the mailing list archives and save everyone some
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org
More information about the Cygwin