* Charles Wilson wrote on Sun, Jun 19, 2005 at 09:28:27PM CEST:
> Ralf Wildenhues wrote:
>
> >a) some setup where config.guess returns *msys* not *mingw*
>
> But here's where you lose me
Hey, I'm about as lost as you are. IOW: I'm still trying to gather
information.
This thread[1] looks related. If the MSYS/MinGW people don't want msys
to appear in config.{guess,sub}, I reckon it probably isn't a good idea
to put it in Libtool either.
To put it another way: somebody please ask _them_ about this issue, and
have them come to a coherent answer. And then we'll implement that.
No need to work around one another.
*snip nice explanations*
> So for the rest of us, I'm not sure there IS a difference between MINGW
> and MSYS -- that is, the ENVIRONMENT is the same: if you're running
> libtool, you've got a shell and m4 and stuff, so you're REALLY running
> under MSYS. The question is, what is your TARGET: MSYS-dll-dependent,
> or pure-native-windows.
ACK. The next logical question is whether the msys* one should show up
anywhere at all, or just be hidden in their packages/patches.
> Given the purpose of MSYS, the default target is pure-native-windows
> (what we'd usually call the "cross" target, in that the result runs on a
> pure-native system but the compiler runs under MSYS); the "unusual"
> target is the msys-dependent one (what we'd usually call the "native"
> target, in that the result runs under the same environment as the compiler).
I believe this is what the bug reporter did. A guess only, though.
Regards,
Ralf
[1] http://sourceforge.net/mailarchive/forum.php?thread_id=7509474&forum_id=5123
