2013/8/7 Thorsten Glaser <[email protected]>: > Fabian Greffrath dixit: > >>> introduction that assumes nothing has been installed yet, > >>There should be an msys.bat in your mingw directory. Run this with the > > I don’t even have one ☺ but … > >>Get the lates installer from here to install MinGW/MSYS: > > … this helps, of course – thanks. > >>All that wingw-w64 does in this regard is bundling the whole of MSYS >>into a single zip file. There are no other "tools that come with it". It >>is, however, more convenient to point people to this zip file than >>leading them through the whole download and installations instructions >>for MinGW if they are just interested in the MSYS utilities. ;) > > Ah. Is that amd64-only or will it work with my win2k setup > on “that laptop from 1999”?
No. ;) MinGW-w64 works on i386 host/target, but MinGW-w64 runtime code targets to XP or later AFAIK. > >>Regarding MSYS, I think development has halted when it was considered >>"good enough" to run the majority of ./configure scripts. There is a > > That’s enough for it goals, after all. > >>reimplementation going on called MSYS2 which will be based on the >>current Cygwin development, but I don't know how far this is from > > I don’t think that’s really good because that dropped e.g. Win95 > compatibility… but YMMV ☺ > > I mean, sure, as user I might want to install and use latest Cygwin, > especially if I develop myself, but if I’m an upstream who wants to > also provide Win32 binaries of his applications, using the old and > more compatible versions fulfills my user story better. yeah, I have a problem when using cygwin-1.7 standalone(that is /bin/patch, about path and %PATHEXT%) and finally I fallback to cygwin-1.5. > > bye, > //mirabilos (much too hot these days) > -- > (gnutls can also be used, but if you are compiling lynx for your own use, > there is no reason to consider using that package) > -- Thomas E. Dickey on the Lynx mailing list, about OpenSSL
