From: Charles W. <cwi...@us...> - 2010-09-10 06:01:18
|
Get it here: https://sourceforge.net/projects/mingw/files_beta/Automated%20MinGW%20Installer/mingw-get/mingw-get-0.1-alpha-4/ This release of mingw-get fixes a bug in the earlier self-upgrade functionality, where any runtime error "deleted" mingw-get. (mingw-get and its support file(s) were actually only renamed, but recovery was difficult). Now, "ordinary" errors such as bad command line arguments, failed downloads, missing manifests, etc, will not cause this behavior. However, a catastrophic operating system error may prevent the new auto-recovery code from executing, leaving mingw-get in its "deleted" (e.g. renamed) state. If this occurs, simply do the following: cd /mingw/bin mv mingw-get.exe~ mingw-get.exe cd /mingw/libexec/mingw-get mv mingw-get-0.dll~ mingw-get-0.dll Add --help|-h option: mingw-get [OPTIONS] ACTION package-spec [package-spec ...] Manage MinGW and MSYS installations (Command-line user interface). Options: --help, -h Show this help text --version, -V Show version and licence information Actions: update Update local copy of repository catalogues install Install new packages remove [not implemented] Remove previously installed packages upgrade [not implemented] Upgrade previously installed packages Package Specifications: [subsystem]-name-[component]: msys-bash-doc The 'doc' component of the bash package for MSYS mingw32-gdb All components of the gdb package for MinGW See /mingw/var/lib/mingw-get/data/*.xml for possible package names and the components associated with each. |
From: Chris W. <ch...@qw...> - 2010-09-10 07:46:05
|
Hi Charles, On Fri, 10 Sep 2010, Charles Wilson wrote: > This release of mingw-get fixes a bug in the earlier self-upgrade > functionality, where any runtime error "deleted" mingw-get. Thanks for fixing this! It would be really excellent to get perl (and its dependency libcrypt), autoconf, automake and m4 packaged for mingw-get. Is there anything I can do to help with this? Is there any point in me manually writing manifest files? > Actions: > update Update local copy of repository catalogues > install Install new packages > remove [not implemented] Remove previously installed packages > upgrade [not implemented] Upgrade previously installed packages As others have already requested, I would also love to see a "list" or "search" option, may I submit a patch to implement it? Cheers, Chris. -- _ ___ __ _ / __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK | / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer | \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software | |
From: Charles W. <cwi...@us...> - 2010-09-10 14:11:50
|
On 9/10/2010 3:16 AM, Chris Wilson wrote: > It would be really excellent to get perl (and its dependency libcrypt), > autoconf, automake and m4 packaged for mingw-get. Is there anything I can > do to help with this? Is there any point in me manually writing manifest > files? All of these are already packaged, with manifests written and published, and can be installed by mingw-get: mingw-get update mingw-get install msys-perl msys-m4 autoconf automake See my message from Sep 6 titled "All current MinGW/MSYS packages now available via mingw-get". Or, to get everything that was in the old "MsysDTK" (now called the "MinGW-DTK") which included all of the above plus a lot more, do this mingw-get install mingw-dtk This last is one of the checkboxes in the new mingw-get-inst-20100909 >> Actions: >> update Update local copy of repository catalogues >> install Install new packages >> remove [not implemented] Remove previously installed packages >> upgrade [not implemented] Upgrade previously installed packages > > As others have already requested, I would also love to see a "list" > or "search" option, may I submit a patch to implement it? Of course. I can't guarantee it'll be accepted (as always, that depends on quality!) but all patches will be thoughtfully considered. -- Chuck |
From: Chris W. <ch...@qw...> - 2010-09-11 11:13:12
|
Hi Charles, On Fri, 10 Sep 2010, Charles Wilson wrote: > All of these are already packaged, with manifests written and published, > and can be installed by mingw-get: > > mingw-get update > mingw-get install msys-perl msys-m4 autoconf automake > > See my message from Sep 6 titled "All current MinGW/MSYS packages now > available via mingw-get". Thanks for that! I thought the installer would be distributed with the latest manifests, and I forgot to run mingw-get update, so I didn't see these new packages in the list of manifest files and I could not install Perl that way. After running mingw-get update I could. I'm having some problems using msys-perl, particularly installing modules from CPAN that require native libraries, as perl's config.h seems to be stuffed up and tells perl.h that some system headers (e.g. netinet/in.h, sys/times.h) are available, when in fact they are not, and this causes compilation of anything including perl.h to fail. Does anyone know where this config.h might have come from or where I can get a more useful one? Cheers, Chris. -- _ ___ __ _ / __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK | / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer | \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software | |
From: Charles W. <cwi...@us...> - 2010-09-11 15:02:54
|
On 9/11/2010 7:13 AM, Chris Wilson wrote: > On Fri, 10 Sep 2010, Charles Wilson wrote: >> All of these are already packaged, with manifests written and published, >> and can be installed by mingw-get: >> >> mingw-get update >> mingw-get install msys-perl msys-m4 autoconf automake >> >> See my message from Sep 6 titled "All current MinGW/MSYS packages now >> available via mingw-get". > > Thanks for that! I thought the installer would be distributed with the > latest manifests, Well, it was, as of 20100909. You didn't say, in your original message, exactly how or what you had attempted to do that led you to believe that perl etc were not available. So, I gave the instructions that would work regardless of what version of mingw-get you had installed, or which manifests it had shipped with. > and I forgot to run mingw-get update, so I didn't see > these new packages in the list of manifest files and I could not install > Perl that way. After running mingw-get update I could. This leads me to believe that you weren't actually using mingw-get-0.1-alpha-4, but instead alpha-3. > I'm having some problems using msys-perl, particularly installing modules > from CPAN that require native libraries, as perl's config.h seems to be > stuffed up and tells perl.h that some system headers (e.g. netinet/in.h, > sys/times.h) are available, when in fact they are not, and this causes > compilation of anything including perl.h to fail. Does anyone know where > this config.h might have come from or where I can get a more useful one? Well, a couple of things. MSYS is a "minimal system"; perl is provided only to support the needs of running "package maintainance tools" -- like the autotools. It really isn't intended to be a "do all things" swiss army knife like perl is on most systems. So, I can't guarantee that you'll EVER be able to get CPAN and other perl add-on packages to work, in general. (OTOH, I *did* use CPAN to build and install the *existing* set of extensions that msys-perl ships with). However... perl is an msys program. To build extensions for it, you need to use the msys compiler, NOT the MinGW one. So, you need to mingw-get install msys-dvlpr This installs the "MSYS System Builder" collection. Then, you need to launch msys.bat using the MSYS argument: msys.bat MSYS And then try to use perl/CPAN from *that* shell. It's path and settings will be configured so that 'uname' reports "I'm MSYS" instead of "I'm MinGW", and the msys gcc will be first in that $PATH. *THAT* version of gcc will look in the appropriate places for the msys headers (like <netinet/in.h>) which you just installed as part of the MSYS System Builder. Note that the regular MinGW gcc will never look where those msys-only headers are installed, so you won't "pollute" normal MinGW builds. -- Chuck |
From: Chris W. <ch...@qw...> - 2010-09-11 11:44:48
|
Hi Charles, On Fri, 10 Sep 2010, Charles Wilson wrote: >> As others have already requested, I would also love to see a "list" or >> "search" option, may I submit a patch to implement it? > > Of course. I can't guarantee it'll be accepted (as always, that depends > on quality!) but all patches will be thoughtfully considered. I'd quite like to do the development of this on Linux, using a cross-compiler, as it's a much more comfortable development environment for me. But currently I'm having problems finding the source of mingw's getopt.h. Can anyone point me to where to get it from CVS? Cheers, Chris. -- _ ___ __ _ / __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK | / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer | \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software | |
From: Charles W. <cwi...@us...> - 2010-09-11 15:10:38
|
On 9/11/2010 7:44 AM, Chris Wilson wrote: > I'd quite like to do the development of this on Linux, using a > cross-compiler, as it's a much more comfortable development environment > for me. But currently I'm having problems finding the source of mingw's > getopt.h. Can anyone point me to where to get it from CVS? It's in libmingwex.a, which is part of the mingw-runtime (mingwrt) package. So, grab mingwrt-3.18-mingw32-src.tar.lzma from the download site. If you have a working cross-compiler setup, the mingw-runtime stuff, like the w32api stuff, should already have been installed in your cross-compiler's $host/include and $host/lib area (it's like the libc part of a unix-focused cross compiler). -- Chuck |
From: Keith M. <kei...@us...> - 2010-09-21 02:43:26
|
On 11/09/2010, Charles Wilson <cwi...@us...> wrote: > On 9/11/2010 7:44 AM, Chris Wilson wrote: >> I'd quite like to do the development of this on Linux, using a >> cross-compiler, as it's a much more comfortable development environment >> for me. As it is for me. Indeed, all of my development on mingw-get, up to alpha-3, was done this way, (with gcc-3.4.5). >> But currently I'm having problems finding the source of mingw's >> getopt.h. Can anyone point me to where to get it from CVS? > > It's in libmingwex.a, which is part of the mingw-runtime (mingwrt) > package. So, grab mingwrt-3.18-mingw32-src.tar.lzma from the download site. > > If you have a working cross-compiler setup, the mingw-runtime stuff, > like the w32api stuff, should already have been installed in your > cross-compiler's $host/include and $host/lib area (it's like the libc > part of a unix-focused cross compiler). Chris, I would certainly welcome your input to the development effort, but you might like to hold fire on the list/show/search feature for a couple of weeks. I already have a partial implementation for at least part of that in my own experimental (uncommitted) tree, which I will not be able to progress for another two weeks[*], and it would be a shame for us to duplicate effort. [*] I've been unavailable to progress mingw-get throughout September; many thanks to Chuck for stepping in to fix a bug I left in alpha-3, before my activity became curtailed. -- Regards, Keith. |
From: Roger P. <rog...@gm...> - 2010-09-21 21:52:44
|
> Get it here: > https://sourceforge.net/projects/mingw/files_beta/Automated%20MinGW%20Installer/mingw-get/mingw-get-0.1-alpha-4/ Thanks for the release. Using this is a *pleasure* compared to what installing mingw has been in the past. A few comments, if you don't mind. 1) passing it zero parameters seems to always fail (even from within the "mingw shell"): C:\MinGW\var\lib\mingw-get\data>mingw-get mingw-get: libexec/mingw-get/gui.exe: unable to start application; status = -1 2) might be nice to have something like "mingw-get list installed packages" so we know if we are missing a certain one. 3) might be nice to have something like "mingw-get list dependencies" which outputs like mingw-developer-toolkit: msys-base msys-bison Just for information sake (mostly so that people can find "meta" packages more easily, though this may not be necessary in the end). 4) Ability to specify version, like install libtool -v1.0.11 (or can it do this already? If so it wasn't clear to me). 5) with mingw-get-inst, have an option "add to path" or what not. Thanks so much! -r |
From: Jasper H. <jas...@gm...> - 2010-09-21 22:48:19
|
Roger Pack wrote: > 1) > passing it zero parameters seems to always fail (even from within the > "mingw shell"): > C:\MinGW\var\lib\mingw-get\data>mingw-get > mingw-get: libexec/mingw-get/gui.exe: unable to start application; status = -1 Did you happen to read the readme? Perhaps you should do so. > 2) > might be nice to have something like "mingw-get list installed > packages" so we know if we are missing a certain one. Sure that might be nice. It's also nice to have someone with enough time to program such a feature. > 3) > might be nice to have something like "mingw-get list dependencies" > which outputs like > > mingw-developer-toolkit: > msys-base > msys-bison That's a sound suggestion, though I don't think it will get a high priority from anyone. > 4) > Ability to specify version, like install libtool -v1.0.11 (or can it > do this already? If so it wasn't clear to me). I don't know if this has fallen under the header of "rejected ideas" or if it's under "probably/possibly too much effort for the gain, but who knows". Either way, you can be sure it's no new idea. > 5) > with mingw-get-inst, have an option "add to path" or what not. mingw-get-inst != mingw-get While your willingness to test mingw-get and share your experience afterwards is greatly appreciated, it would help if you - for example - read the readme before doing so. Also, taking a quick look through the mailing list archives wouldn't hurt either. Jasper |
From: Charles W. <cwi...@us...> - 2010-09-22 03:10:19
|
On 9/21/2010 6:47 PM, Jasper Horn wrote: > Roger Pack wrote: >> 1) >> passing it zero parameters seems to always fail (even from within the >> "mingw shell"): >> C:\MinGW\var\lib\mingw-get\data>mingw-get >> mingw-get: libexec/mingw-get/gui.exe: unable to start application; status = -1 > > Did you happen to read the readme? Perhaps you should do so. To be fair, it's on my todo list to make this error message a bit more explanatory, at least until we actually HAVE a gui mode. >> 2) >> might be nice to have something like "mingw-get list installed >> packages" so we know if we are missing a certain one. > > Sure that might be nice. It's also nice to have someone with enough > time to program such a feature. Well, Chris has already indicated interest in doing this, and Keith has a partially-completed implementation in his sandbox right now. So...we'll get there. >> 3) >> might be nice to have something like "mingw-get list dependencies" >> which outputs like >> >> mingw-developer-toolkit: >> msys-base >> msys-bison > > That's a sound suggestion, though I don't think it will get a high > priority from anyone. Actually, list --requires (or --dependencies or whatever) is no more difficult to implement than the regular list/show/search mode, IIUC. And most package managers support something similar, so I reckon it'll get implemented at some point. >> 4) >> Ability to specify version, like install libtool -v1.0.11 (or can it >> do this already? If so it wasn't clear to me). > > I don't know if this has fallen under the header of "rejected ideas" > or if it's under "probably/possibly too much effort for the gain, but > who knows". Either way, you can be sure it's no new idea. I think this is pretty difficult to implement, and certainly less important than fixing the severe usability problems we currently have. (list/show mode, a gui...) But...at some point, implementing this should be possible. Don't hold your breath, tho. It'll probably be a while. >> 5) >> with mingw-get-inst, have an option "add to path" or what not. This is a good idea. I'll try to update mingw-get-inst in the next week or so. -- Chuck |
From: Roger P. <rog...@gm...> - 2010-09-22 20:15:59
|
> Did you happen to read the readme? Perhaps you should do so. Hmm. I have a suggestion for the readme: split it into a "history.txt" and separate "readme" (or have only the latest changes mentioned in there). Thanks! >> 5) >> with mingw-get-inst, have an option "add to path" or what not. > > mingw-get-inst != mingw-get > > While your willingness to test mingw-get and share your experience > afterwards is greatly appreciated, it would help if you - for example > - read the readme before doing so. Also, taking a quick look through > the mailing list archives wouldn't hurt either. This was a comment about mingw-get-inst (I tried them both BTW). Cheers! -r |