The uname function is supplied via the MSYS (Minimal SYStem) and a separate function isn't necessary. Also, if
not using MSYS when configuring you can also specify the host, build and target on the command line so that
config.guess isn't even invoked.
However, I thank you for your interest in the MinGW project and look forward to more contributions from you.
Earnie.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is not an uname *function*, but an uname *executable*.
Having such an executable means that ./configure "just
works", which surely is an improvement over having to
explicitely specify a target.
Furthermore, when used together with Cygwin - which the Web
page certainly suggests - the Cygwin uname misleads
configure scripts, unless there is another uname in the PATH
before it.
So it seems to me that an uname executable does belong in
the MinGW base package.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
uname.c
Logged In: YES
user_id=15438
The uname function is supplied via the MSYS (Minimal SYStem) and a separate function isn't necessary. Also, if
not using MSYS when configuring you can also specify the host, build and target on the command line so that
config.guess isn't even invoked.
However, I thank you for your interest in the MinGW project and look forward to more contributions from you.
Earnie.
Logged In: YES
user_id=421250
This is not an uname *function*, but an uname *executable*.
Having such an executable means that ./configure "just
works", which surely is an improvement over having to
explicitely specify a target.
Furthermore, when used together with Cygwin - which the Web
page certainly suggests - the Cygwin uname misleads
configure scripts, unless there is another uname in the PATH
before it.
So it seems to me that an uname executable does belong in
the MinGW base package.