From: Peter J. F. I. <pjf...@ea...> - 2008-04-14 00:05:23
|
My most sincere apologies to the whole list for sending the prior version of this email in HTML. Mea maxima culpa! I forgot to set my mail client to plain text. Hopefully this will come to you plain text as it should have in the first place. Hi all, I have been reading as many messages related to installation of msys as I can in the mingw-msys archive, but I did not see any posts that describe which MSYS-1.0.11 files should be installed in which order to update a base msys-1.0.10 system to whatever the current state of msys-1.0.11 may or should be. I have used MinGW-5.1.3.exe to install gcc and g++, then installed MSYS-1.0.11.exe as recommended. My directory structure is also as recommended, c:\msys\1.0 for msys and c:\msys\1.0\mingw for gcc and g++. I DL'd and ran msysDTK-1.0.1.exe as well. Now I would like to update to msys-1.0.11 as far as possible, so I DL'd all the "Technology Preview" *.tar.gz or *.tar.bz2 files on the download page under MSYS Base System, but there isn't a reference anywhere I could find that indicates in what order these archives should be installed, if any order is needed. In particular, I now have both msysCORE-1.0.11-2007.01.19-1.tar.bz2 and coreutils-5.97-MSYS-1.0.11-snapshot.tar.bz2. The msysCORE archive seems to have about half the utilities dated 2002 and 2003 and the rest in January 2007, while the base msys-1.1.10 installed all the core utilities dated in March 2004. The coreutilis snapshot has many of the same utilities (but not all of them) dated in August 2007. Plus the coreutils snapshot has a different directory structure, with an extra level named "coreutils-5.97" above the bin/doc/info/lib directories. So should the msysCORE be installed first and the coreutils snapshot laid over that? Should the coreutils contents be copied after extracting the archive to the regular msys directories? What about the individual utility sets like findutils and diffutils? Should they be installed over the msysCORE and coreutils snapshot, or instead of one or both of them, or not at all? And I have similar questions for the DTK utilities. Should I use autoconf-2.5-2.61 or autoconf-2.1-2.13? automake-1.9 or automake-1.10 or automake-3-1? Should I install gettext-1.16.1-1.bin or gettext-0.16.1-MSYS-1.0.11-1? If there is a page or a message or set of messages I need to read to clear up my confusion, please point me to them and I will do so. TIA for any help you can provide. Regards, Peter |
From: Cesar S. <ces...@gm...> - 2008-04-14 01:59:42
|
Peter J. Farley III wrote: > So should the msysCORE be installed first and the coreutils snapshot > laid over that? Should the coreutils contents be copied after > extracting the archive to the regular msys directories? Correct on both accounts. > What about the individual utility sets like findutils and diffutils? > Should they be installed over the msysCORE and coreutils snapshot, or > instead of one or both of them, or not at all? They should be installed over. > > And I have similar questions for the DTK utilities. Should I use > autoconf-2.5-2.61 or autoconf-2.1-2.13? automake-1.9 or automake-1.10 > or automake-3-1? Should I install gettext-1.16.1-1.bin or > gettext-0.16.1-MSYS-1.0.11-1? > You can safely install all of the above. automake-3-1 is a wrapper script which calls autoconf-2.5-2.61 or autoconf-2.1-2.13 as appropriate, dependent on the requirements of the particular source package you are building. Likewise for automake-3-1. As for gettext-1.16.1-1-bin, it provides autopoint, which is another autotool you may need. The gettext-0.16.1-MSYS-1.0.11-1, on the other hand, is a MSYS build. You can install it as well, other MSYS-built tools may depend on it. Note that you don't need to install all of the DTK tools, you can pick those you really need. You may find, however, that some tools have dependencies you need to install as well. A safe bet is to install them all. Regards, Cesar |
From: Peter J. F. I. <pjf...@ea...> - 2008-04-14 02:44:36
|
On Sun, 13 Apr 2008 22:59:26 -0200, Cesar Strauss wrote: > Peter J. Farley III wrote: >> So should the msysCORE be installed first and the coreutils >> snapshot laid over that? Should the coreutils contents be copied >> after extracting the archive to the regular msys directories? > > Correct on both accounts. Thanks for the reply and the confirmation. >> What about the individual utility sets like findutils and >> diffutils? Should they be installed over the msysCORE and >> coreutils snapshot, or instead of one or both of them, or not at >> all? > > They should be installed over. Thanks again. >> And I have similar questions for the DTK utilities. Should I use >> autoconf-2.5-2.61 or autoconf-2.1-2.13? automake-1.9 or automake- >> 1.10 or automake-3-1? Should I install gettext-1.16.1-1.bin or >> gettext-0.16.1-MSYS-1.0.11-1? >> >> > You can safely install all of the above. automake-3-1 is a wrapper > script which calls autoconf-2.5-2.61 or autoconf-2.1-2.13 as > appropriate, dependent on the requirements of the particular source > package you are building. Likewise for automake-3-1. > > As for gettext-1.16.1-1-bin, it provides autopoint, which is > another autotool you may need. The gettext-0.16.1-MSYS-1.0.11-1, on > the other hand, is a MSYS build. You can install it as well, other > MSYS-built tools may depend on it. I'm a bit confused. Aren't all the tools in that directory MSYS builds? Or are only the ones marked MSYS truly MSYS builds? If so, does that mean the *-bin-* builds are for mingw only, and therefore should go into the mingw/bin directory, as opposed to the msys/bin directory? > Note that you don't need to install all of the DTK tools, you can > pick those you really need. You may find, however, that some tools > have dependencies you need to install as well. A safe bet is to > install them all. Yes, that would be a my thought as well. I like a robust build environment that will handle whatever I need to throw at it. BTW, is there an easier way than the sourceforge DL pages to get all those files one by one? Could I use wget and put together a script to just get them all at one go? If so, what would I use for the url? Or is there an ftp alternative? Many thanks for your cogent and prompt answers. Regards, Peter |
From: Brian D. <br...@de...> - 2008-04-14 03:07:38
|
"Peter J. Farley III" wrote: > I'm a bit confused. Aren't all the tools in that directory MSYS > builds? Or are only the ones marked MSYS truly MSYS builds? > > If so, does that mean the *-bin-* builds are for mingw only, and > therefore should go into the mingw/bin directory, as opposed to the > msys/bin directory? There are two flavors of the autotools, see <http://thread.gmane.org/gmane.comp.gnu.mingw.msys/4309/focus=4324>. > BTW, is there an easier way than the sourceforge DL pages to get all > those files one by one? Could I use wget and put together a script to > just get them all at one go? If so, what would I use for the url? Or > is there an ftp alternative? wget works just fine with sourceforge, e.g. $ for pkg in autoconf-2.61 automake-1.10 libiconv-1.11 \ gettext-0.16.1 gettext-devel-0.16.1; do \ wget -nv \ http://downloads.sourceforge.net/mingw/$pkg-MSYS-1.0.11.tar.bz2; \ done The downloads.sourceforge.net URL above will http-redirect to a random mirror. You can also just pick your desired mirror URL and use that directly as sometimes you get redirected to a mirror very far from you. Brian |
From: Peter J. F. I. <pjf...@ea...> - 2008-04-14 06:27:31
|
On Sun, 13 Apr 2008 20:09:33 -0700, Brian Dessent wrote: > There are two flavors of the autotools, see > <http://thread.gmane.org/gmane.comp.gnu.mingw.msys/4309/focus=4324>. OK, that's *much* clearer now. Thanks a lot for the link. <Snipped> > wget works just fine with sourceforge, e.g. > > $ for pkg in autoconf-2.61 automake-1.10 libiconv-1.11 \ > gettext-0.16.1 gettext-devel-0.16.1; do \ > wget -nv \ > http://downloads.sourceforge.net/mingw/$pkg-MSYS-1.0.11.tar.bz2; \ > done > > The downloads.sourceforge.net URL above will http-redirect to a > random mirror. You can also just pick your desired mirror URL and > use that directly as sometimes you get redirected to a mirror very > far from you. And thanks for that as well. Regards, Peter |