From: Chris S. <ir0...@gm...> - 2011-01-23 03:23:23
|
I've uploaded mingw32-make-3.82-5 that is dynamically linked to libintl as opposed to statically linking it, thereby reducing the size of the mingw32-make binary. I have configured mingw32-make with the following options: --program-prefix=mingw32- --prefix=/mingw --target=mingw32 --host=mingw32 --enable-case-insensitive-file-system --disable-job-server To manually update, the files are: http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-bin.tar.lzma/download http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-doc.tar.lzma/download http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-lang.tar.lzma/download The source is available here: http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-src.tar.lzma/download To upgrade via the installer: mingw-get update mingw-get upgrade mingw32-make I've added libintl as a requirement for the latest release, so mingw-get will pull down the necessary dependencies as well. Please report any issues to the mingw-users mailing list. Chris |
From: Peter R. <p.r...@sh...> - 2011-01-23 18:58:51
|
On 23/01/2011 03:23, Chris Sutcliffe wrote: > I've uploaded mingw32-make-3.82-5 that is dynamically linked to libintl as opposed to statically linking it, thereby reducing the size of the mingw32-make binary. I have configured mingw32-make with the following options: > > --program-prefix=mingw32- > --prefix=/mingw > --target=mingw32 > --host=mingw32 > --enable-case-insensitive-file-system > --disable-job-server > > To manually update, the files are: > > http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-bin.tar.lzma/download > http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-doc.tar.lzma/download > http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-lang.tar.lzma/download > > The source is available here: > > http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.82-mingw32/make-3.82-5-mingw32-src.tar.lzma/download > > To upgrade via the installer: > > mingw-get update > mingw-get upgrade mingw32-make > > I've added libintl as a requirement for the latest release, so mingw-get will pull down the necessary dependencies as well. > > Please report any issues to the mingw-users mailing list. > > Chris > When I install this upgrade and try to run it, I get an error saying "libiconv-2.dll not found"! Has this been left off the (new) dependencies manifest? (After installing libiconv using mingw-get, make now works properly.) P. |
From: Chris S. <ir0...@gm...> - 2011-01-23 20:20:39
|
On 23/01/2011 1:58 PM, Peter Rockett wrote: > When I install this upgrade and try to run it, I get an error saying > "libiconv-2.dll not found"! Has this been left off the (new) > dependencies manifest? Interesting, when I run 'mingw-get upgrade mingw32-make' I see: no change: libiconv-1.13.1-1-mingw32-dll-2.tar.lzma no change: libintl-0.17-1-mingw32-dll-8.tar.lzma upgrade: make-3.82-5-mingw32-bin.tar.lzma removing make-3.82-4-mingw32-bin.tar.lzma so it does check libiconv for me. Chuck / Keith, any ideas? Chris |
From: Peter R. <p.r...@sh...> - 2011-01-23 21:34:48
|
On 23/01/2011 20:20, Chris Sutcliffe wrote: > On 23/01/2011 1:58 PM, Peter Rockett wrote: >> When I install this upgrade and try to run it, I get an error saying >> "libiconv-2.dll not found"! Has this been left off the (new) >> dependencies manifest? > Interesting, when I run 'mingw-get upgrade mingw32-make' I see: > > no change: libiconv-1.13.1-1-mingw32-dll-2.tar.lzma > no change: libintl-0.17-1-mingw32-dll-8.tar.lzma > upgrade: make-3.82-5-mingw32-bin.tar.lzma > removing make-3.82-4-mingw32-bin.tar.lzma > > so it does check libiconv for me. > > Chuck / Keith, any ideas? > > Chris > I get this now too. But not sure what I got before manually installing libiconv. BTW: I have a new install. I will repeat this upgrade procedure tomorrow on another clean install to see what happens. P. |
From: Keith M. <kei...@us...> - 2011-01-23 21:58:16
|
On 23/01/11 21:34, Peter Rockett wrote: > BTW: I have a new install. I will repeat this upgrade procedure > tomorrow on another clean install to see what happens. For a clean install, you should be using `mingw-get install' anyway, *not* `mingw-get upgrade'. Apart from this, there appears to be a bug in `mingw-get upgrade', (see my earlier post), so `mingw-get install' is to be preferred until I can fix it. -- Regards, Keith |
From: Peter R. <p.r...@sh...> - 2011-01-24 09:00:32
|
On 23/01/11 21:58, Keith Marshall wrote: > On 23/01/11 21:34, Peter Rockett wrote: >> BTW: I have a new install. I will repeat this upgrade procedure >> tomorrow on another clean install to see what happens. > For a clean install, you should be using `mingw-get install' anyway, > *not* `mingw-get upgrade'. Apart from this, there appears to be a bug > in `mingw-get upgrade', (see my earlier post), so `mingw-get install' > is to be preferred until I can fix it. > Just to clarify: I have a second MinGW install which was created ab initio using mingw-get install _before_ the latest make upgrade. I was going to run the upgrade on that and have a close look at the upgrade messages. P. |
From: Keith M. <kei...@us...> - 2011-01-26 11:28:21
|
On 24 January 2011 09:00, Peter Rockett wrote: > On 23/01/11 21:58, Keith Marshall wrote: >> On 23/01/11 21:34, Peter Rockett wrote: >>> BTW: I have a new install. I will repeat this upgrade procedure >>> tomorrow on another clean install to see what happens. >> For a clean install, you should be using `mingw-get install' anyway, >> *not* `mingw-get upgrade'. Apart from this, there appears to be a bug >> in `mingw-get upgrade', (see my earlier post), so `mingw-get install' >> is to be preferred until I can fix it. > > Just to clarify: I have a second MinGW install which was created ab > initio using mingw-get install _before_ the latest make upgrade. Okay. That makes more sense now; it is also a perfectly reasonable sequence of actions. > I was going to run the upgrade on that and have a close look at the > upgrade messages. By all means do so, if you wish, but I believe I have reproduced the problem, and have identified the cause -- the "upgrade" operation is currently failing to schedule an "install", where a package which is being upgraded introduces a new dependency, on any prerequisite which had not previously been installed. It will not be difficult to fix; I hope to upload a corrected build by the end of this week. -- Regards, Keith. |
From: Peter R. <p.r...@sh...> - 2011-01-26 12:26:37
|
On 26/01/11 11:28, Keith Marshall wrote: > On 24 January 2011 09:00, Peter Rockett wrote: >> On 23/01/11 21:58, Keith Marshall wrote: >>> On 23/01/11 21:34, Peter Rockett wrote: >>>> BTW: I have a new install. I will repeat this upgrade procedure >>>> tomorrow on another clean install to see what happens. >>> For a clean install, you should be using `mingw-get install' anyway, >>> *not* `mingw-get upgrade'. Apart from this, there appears to be a bug >>> in `mingw-get upgrade', (see my earlier post), so `mingw-get install' >>> is to be preferred until I can fix it. >> Just to clarify: I have a second MinGW install which was created ab >> initio using mingw-get install _before_ the latest make upgrade. > Okay. That makes more sense now; it is also a perfectly reasonable > sequence of actions. > >> I was going to run the upgrade on that and have a close look at the >> upgrade messages. > By all means do so, if you wish, but I believe I have reproduced the > problem, and have identified the cause -- the "upgrade" operation is > currently failing to schedule an "install", where a package which is > being upgraded introduces a new dependency, on any prerequisite which > had not previously been installed. That makes perfect sense. > It will not be difficult to fix; I hope to upload a corrected build by > the end of this week. > Excellent! (In the end I didn't run the test I mentioned because when I looked closely, I had explicitly installed libiconv on the machine in question. So the test would have told me nothing useful.) BTW: Maybe one for Chris Sutcliffe - why does "mingw32-make -v" respond with just version 3.82? In the course of all this I was trying confirm which version of mingw32-make I had just installed and was frustrated to find I could not differentiate between 3.82-4 and 3.82-5. Can mingw32-make be altered to report the minor-minor version number (or whatever it is)? P. |
From: Chris S. <ir0...@gm...> - 2011-01-26 12:45:49
|
On 26 January 2011 07:26, Peter Rockett wrote: > BTW: Maybe one for Chris Sutcliffe - why does "mingw32-make -v" respond > with just version 3.82? In the course of all this I was trying confirm > which version of mingw32-make I had just installed and was frustrated to > find I could not differentiate between 3.82-4 and 3.82-5. Can > mingw32-make be altered to report the minor-minor version number (or > whatever it is)? I'll have a look the next time I package 'make'. Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d |
From: Keith M. <kei...@us...> - 2011-01-26 13:30:13
|
On 26 January 2011 12:26, Peter Rockett wrote: > Can mingw32-make be altered to report the minor-minor version > number (or whatever it is)? I'll leave Chris to follow up on that; (he's already said he will). As far as terminology is concerned, our packaging documentation refers to this as a "build serial number": http://mingw.org/PackageIdentificationHOWTO -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2011-02-10 21:30:00
|
On 26/01/11 11:28, Keith Marshall wrote: > ... the "upgrade" operation is currently failing to schedule an > "install", where a package which is being upgraded introduces a new > dependency, on any prerequisite which had not previously been > installed. > > It will not be difficult to fix; I hope to upload a corrected build > by the end of this week. Well, the prolonged SF outage scuppered that plan! They still haven't brought CVS back, but with file uploads available again, I don't want to delay this any longer. I've uploaded the fix today; you may find it in the mingw-get-0.1-mingw32-alpha-5.1 package set. -- Regards, Keith |
From: Charles W. <cwi...@us...> - 2011-02-10 22:48:11
|
On 2/10/2011 4:29 PM, Keith Marshall wrote: > On 26/01/11 11:28, Keith Marshall wrote: >> ... the "upgrade" operation is currently failing to schedule an >> "install", where a package which is being upgraded introduces a new >> dependency, on any prerequisite which had not previously been >> installed. >> >> It will not be difficult to fix; I hope to upload a corrected build >> by the end of this week. > > Well, the prolonged SF outage scuppered that plan! They still haven't > brought CVS back, but with file uploads available again, I don't want to > delay this any longer. I've uploaded the fix today; you may find it in > the mingw-get-0.1-mingw32-alpha-5.1 package set. OK, I'll update mingw-get-inst-$NEXT to use that package and upload it as well. Give me a day or two. -- Chuck |
From: Peter R. <p.r...@sh...> - 2011-02-11 10:25:10
|
On 10/02/11 21:29, Keith Marshall wrote: > On 26/01/11 11:28, Keith Marshall wrote: >> ... the "upgrade" operation is currently failing to schedule an >> "install", where a package which is being upgraded introduces a new >> dependency, on any prerequisite which had not previously been >> installed. >> >> It will not be difficult to fix; I hope to upload a corrected build >> by the end of this week. > Well, the prolonged SF outage scuppered that plan! They still haven't > brought CVS back, but with file uploads available again, I don't want to > delay this any longer. I've uploaded the fix today; you may find it in > the mingw-get-0.1-mingw32-alpha-5.1 package set. If I'm right, mingw-get should upgrade itself recursively? In other words, will 'mingw-get update' followed by 'mingw-get upgrade mingw-get' should work. This doesn't seem to work for me. The file creation dates on neither the exe nor the dll change. P. |
From: Keith M. <kei...@us...> - 2011-02-11 12:23:38
|
On 11 February 2011 10:25, Peter Rockett <p.r...@sh...> wrote: > If I'm right, mingw-get should upgrade itself recursively? It should, yes. > In other words, will [sic] 'mingw-get update' followed by > 'mingw-get upgrade mingw-get' should work. Yes. > This doesn't seem to work for me. Hmm. It did for me, yesterday, just before I uploaded the new packages. > The file creation dates on neither the exe nor the dll change. What does 'mingw-get --version' say? What does the content of 'c:/MinGW/var/lib/mingw-get/data/mingw32-mingw-get.xml'[*] look like, after your 'mingw-get update'? [*] If you've installed mingw-get into some prefix other than c:/MinGW, (i.e. if mingw-get.exe lives somewhere other than at c:/MinGW/bin/mingw-get.exe), please adjust the prefix to match your installation. -- Regards, Keith. |
From: Peter R. <p.r...@sh...> - 2011-02-11 12:53:33
|
On 11/02/11 12:23, Keith Marshall wrote: > On 11 February 2011 10:25, Peter Rockett<p.r...@sh...> wrote: >> If I'm right, mingw-get should upgrade itself recursively? > It should, yes. >> In other words, will [sic] 'mingw-get update' followed by >> 'mingw-get upgrade mingw-get' should work. > Yes. >> This doesn't seem to work for me. > Hmm. It did for me, yesterday, just before I uploaded > the new packages. > >> The file creation dates on neither the exe nor the dll change. > What does 'mingw-get --version' say? 'version 0.1-alpha-5' NB. No '.1' suffix. > What does the content of > 'c:/MinGW/var/lib/mingw-get/data/mingw32-mingw-get.xml'[*] look > like, after your 'mingw-get update'? I have cracked one part of the problem: Before I was running mingw-get as a power-user whereas I had previously installed mingw as admin. My power user account did not have write permissions on the xml file so this was not being updated properly. (Possibly a feature request :-) : mingw-get does not appear to report file access violations?) That said, running the update as admin, I now have an mingw-get.xml file that looks right - it lists the '...-alpha-5.1' tarball. But the upgrade still does not work. > [*] If you've installed mingw-get into some prefix other than > c:/MinGW, (i.e. if mingw-get.exe lives somewhere other than at > c:/MinGW/bin/mingw-get.exe), please adjust the prefix to match > your installation. > I have it all in c:/mingw so the exe lives in the place you have specified. P. |
From: Keith M. <kei...@us...> - 2011-02-11 17:10:07
|
On 11 February 2011 12:53, Peter Rockett <p.r...@sh...> wrote: > I have cracked one part of the problem: Before I was running mingw-get > as a power-user whereas I had previously installed mingw as admin. My > power user account did not have write permissions on the xml file so > this was not being updated properly. (Possibly a feature request :-) : > mingw-get does not appear to report file access violations?) Oh, let's just call it as it is: it's another bug! You might like to file a ticket on the tracker, lest I forget. > That said, running the update as admin, I now have an mingw-get.xml > file that looks right - it lists the '...-alpha-5.1' tarball. Good. > But the upgrade still does not work. That's odd. It works for me (after reverting to alpha-5): $ mingw-get --version mingw-get version 0.1-alpha-5 Copyright (C) 2009, 2010, MinGW Project This is free software; see the product documentation, or source code, for copying and redistribution conditions. There is NO WARRANTY; not even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY PARTICULAR PURPOSE. $ mingw-get update Load catalogue: ... Load catalogue: .../var/lib/mingw-get/data/mingw32-mingw-get.xml Load catalogue: ... $ mingw-get --version mingw-get version 0.1-alpha-5 Copyright (C) 2009, 2010, MinGW Project ... $ mingw-get upgrade mingw-get Load catalogue: ... Load catalogue: .../var/lib/mingw-get/data/mingw32-mingw-get.xml Load catalogue: ... upgrade: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz removing mingw-get-0.1-mingw32-alpha-5-bin.tar.gz upgrade: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz removing mingw-get-0.1-mingw32-alpha-5-lic.tar.gz $ mingw-get --version mingw-get version 0.1-alpha-5.1 Copyright (C) 2009, 2010, 2011, MinGW Project This is free software; see the product documentation, or source code, for copying and redistribution conditions. There is NO WARRANTY; not even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY PARTICULAR PURPOSE. -- Regards, Keith. |
From: Peter R. <p.r...@sh...> - 2011-02-12 09:08:39
|
On 11/02/11 17:01, Keith Marshall wrote: > On 11 February 2011 12:53, Peter Rockett<p.r...@sh...> wrote: >> I have cracked one part of the problem: Before I was running mingw-get >> as a power-user whereas I had previously installed mingw as admin. My >> power user account did not have write permissions on the xml file so >> this was not being updated properly. (Possibly a feature request :-) : >> mingw-get does not appear to report file access violations?) > Oh, let's just call it as it is: it's another bug! I prefer to call it a "sub-optimal feature". :-) But maybe I have spent too long on MSDN... > You might like to > file a ticket on the tracker, lest I forget. I would if I could work-out how to file such a report! Am I overlooking some link somewhere? (And, yes, I did login to SF.) >> That said, running the update as admin, I now have an mingw-get.xml >> file that looks right - it lists the '...-alpha-5.1' tarball. > Good. > >> But the upgrade still does not work. > That's odd. It works for me (after reverting to alpha-5): > > $ mingw-get --version > mingw-get version 0.1-alpha-5 > Copyright (C) 2009, 2010, MinGW Project > > This is free software; see the product documentation, or source code, > for copying and redistribution conditions. There is NO WARRANTY; not > even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY > PARTICULAR PURPOSE. > > $ mingw-get update > Load catalogue: ... > Load catalogue: .../var/lib/mingw-get/data/mingw32-mingw-get.xml > Load catalogue: ... > > $ mingw-get --version > mingw-get version 0.1-alpha-5 > Copyright (C) 2009, 2010, MinGW Project > > ... > > $ mingw-get upgrade mingw-get > Load catalogue: ... > Load catalogue: .../var/lib/mingw-get/data/mingw32-mingw-get.xml > Load catalogue: ... > upgrade: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz > removing mingw-get-0.1-mingw32-alpha-5-bin.tar.gz > upgrade: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz > removing mingw-get-0.1-mingw32-alpha-5-lic.tar.gz > > $ mingw-get --version > mingw-get version 0.1-alpha-5.1 > Copyright (C) 2009, 2010, 2011, MinGW Project > > This is free software; see the product documentation, or source code, > for copying and redistribution conditions. There is NO WARRANTY; not > even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY > PARTICULAR PURPOSE. > I have two WinXP machines, one at home and one at work. Both identical MinGW installs from mingw-get. Same virus checkers, etc. The issue above relates to the work machine: I get the same as Keith up to but not including the upgrade/removing lines. I have tried running the same upgrade procedure on my home machine.... and you guessed it! Runs perfectly! Hmmmmm.... Will try again on Monday + try it on a different machine at work. P. |
From: Albrecht S. <vms...@go...> - 2011-02-18 13:25:19
|
On 12.02.2011 10:08, Peter Rockett wrote: > I have two WinXP machines, one at home and one at work. Both identical > MinGW installs from mingw-get. Same virus checkers, etc. The issue above > relates to the work machine: I get the same as Keith up to but not > including the upgrade/removing lines. Same here on Win 7: mingw-get update loaded the files, and the file: /mingw/var/lib/mingw-get/data/mingw32-mingw-get.xml contains: ... <component class="bin"> <release tarname="mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz" /> <release tarname="mingw-get-0.1-mingw32-alpha-5-bin.tar.gz" /> <release tarname="mingw-get-0.1-mingw32-alpha-4-bin.tar.gz" /> <release tarname="mingw-get-0.1-mingw32-alpha-3-bin.tar.gz" /> </component> <component class="lic"> <release tarname="mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz" /> <release tarname="mingw-get-0.1-mingw32-alpha-5-lic.tar.gz" /> <release tarname="mingw-get-0.1-mingw32-alpha-4-lic.tar.gz" /> <release tarname="mingw-get-0.1-mingw32-alpha-3-lic.tar.gz" /> </component> </package> ... "mingw-get upgrade mingw-get" shows only the "Load catalogue" lines, whereas "mingw-get install mingw-get" also did: downloading: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz: 218013 b downloading: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz: 16974 b install: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz install: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz Now "mingw-get --version" also shows: mingw-get version 0.1-alpha-5.1 Additional note: now, after the upgrade, I can see: $ mingw-get upgrade mingw-get Load catalogue: C:\MinGW\var/lib/mingw-get/data/package-list.xml ... Load catalogue: C:\MinGW\var/lib/mingw-get/data/msys-system-builder.xml upgrade: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz FIXME:pkgRemove<stub>:not removing mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz installing mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz upgrade: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz FIXME:pkgRemove<stub>:not removing mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz installing mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz Albrecht |
From: Charles W. <cwi...@us...> - 2011-01-26 13:33:37
|
On 1/26/2011 7:26 AM, Peter Rockett wrote: > Can > mingw32-make be altered to report the minor-minor version number (or > whatever it is)? Well, that's up to Chris -- but I doubt any of the other packages will be modified to report their msys or mingw "release" number. There are other tools: 1) look at /mingw/share/doc/MinGW/$PKG.RELEASE_NOTES.txt or /usr/share/doc/MSYS/$PKG.RELEASE_NOTES.txt That file will usually indicate the "release" number 2) Eventually, mingw-get will have a mode to list the version/release number of all installed (or a specific installed) packages... -- Chuck |
From: Chris S. <ir0...@gm...> - 2011-01-26 13:56:50
|
On 26 January 2011 08:33, Charles Wilson wrote: > On 1/26/2011 7:26 AM, Peter Rockett wrote: >> Can >> mingw32-make be altered to report the minor-minor version number (or >> whatever it is)? > > Well, that's up to Chris -- but I doubt any of the other packages will > be modified to report their msys or mingw "release" number. Agreed, and I really do not want to maintain local patches (i.e. I prefer to stick with 'vanilla' sources as much as possible). If the version number can be overridden via a configure option or by feeding it in to the makefile, I'll do so. If it requires a code change, I do not plan on implementing that. Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d |
From: Keith M. <kei...@us...> - 2011-01-26 14:05:47
|
On 26 January 2011 13:33, Charles Wilson wrote: > 2) Eventually, mingw-get will have a mode to list the version/release > number of all installed (or a specific installed) packages... In fact, CVS head *already* has a first pass implementation of code to do something along those lines -- it will display version info for any one specified component package at a time. I have other features planned for the next formal release, but anyone who would like to preview this is welcome to build a CVS snapshot for themselves. -- Regards, Keith. |
From: Peter R. <p.r...@sh...> - 2011-02-14 11:12:18
|
>>> But the upgrade still does not work. >> That's odd. It works for me (after reverting to alpha-5): >> >> $ mingw-get --version >> mingw-get version 0.1-alpha-5 >> Copyright (C) 2009, 2010, MinGW Project >> >> This is free software; see the product documentation, or source code, >> for copying and redistribution conditions. There is NO WARRANTY; not >> even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY >> PARTICULAR PURPOSE. >> >> $ mingw-get update >> Load catalogue: ... >> Load catalogue: .../var/lib/mingw-get/data/mingw32-mingw-get.xml >> Load catalogue: ... >> >> $ mingw-get --version >> mingw-get version 0.1-alpha-5 >> Copyright (C) 2009, 2010, MinGW Project >> >> ... >> >> $ mingw-get upgrade mingw-get >> Load catalogue: ... >> Load catalogue: .../var/lib/mingw-get/data/mingw32-mingw-get.xml >> Load catalogue: ... >> upgrade: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz >> removing mingw-get-0.1-mingw32-alpha-5-bin.tar.gz >> upgrade: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz >> removing mingw-get-0.1-mingw32-alpha-5-lic.tar.gz >> >> $ mingw-get --version >> mingw-get version 0.1-alpha-5.1 >> Copyright (C) 2009, 2010, 2011, MinGW Project >> >> This is free software; see the product documentation, or source code, >> for copying and redistribution conditions. There is NO WARRANTY; not >> even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY >> PARTICULAR PURPOSE. >> > I have two WinXP machines, one at home and one at work. Both identical > MinGW installs from mingw-get. Same virus checkers, etc. The issue above > relates to the work machine: I get the same as Keith up to but not > including the upgrade/removing lines. > > I have tried running the same upgrade procedure on my home machine.... > and you guessed it! Runs perfectly! Hmmmmm.... Will try again on Monday > + try it on a different machine at work. > > P. > I have now tried this on three different machines at work. Same result: the upgrade fails (silently) on all three. All 3 machines are the nominally the same as my home machine. The only obvious difference is the network connection. (At home I have broadband.) Keith - Any thoughts on how to progress this? I haven't looked through the source code but I was wondering if generating the debug build of mingw-get-alpha-5 and stepping through might help. But may needs me guidance on what to look for. P. |
From: Peter R. <p.r...@sh...> - 2011-02-14 13:39:33
|
On 14/02/11 12:55, Chris Sutcliffe wrote: > On 14 February 2011 06:12, Peter Rockett wrote: >> I have now tried this on three different machines at work. Same result: >> the upgrade fails (silently) on all three. All 3 machines are the >> nominally the same as my home machine. > I had the same issue and got around it by: > > mingw-get install mingw-get > > Chris > Sure, that fix occurred to me but the 'upgrade' path _should_ work. Interesting that you have the same problem though. Are you downloading via broadband or a corporate LAN? P. |
From: Peter R. <p.r...@sh...> - 2011-02-14 15:15:07
|
On 14/02/11 12:53, Keith Marshall wrote: > On 14 February 2011 11:12, Peter Rockett wrote: >> I have now tried this on three different machines at work. Same result: >> the upgrade fails (silently) on all three. All 3 machines are the >> nominally the same as my home machine. >> >> The only obvious difference is the network connection. (At home I have >> broadband.) > And at work? A shared connection via an authenticating proxy, perhaps? Errr.... a socket on the wall wot works at 100MB/s :-[ . Part of the JISC UK academic network but what happens twixt the leased fibre optic and the socket in my office falls into the 'life is too short' category. If it's important I can find-out but locating the right person in our computing services department will be not a trivial matter. >> Keith - Any thoughts on how to progress this? > If we review Friday's dialogue: >>>> It works for me (after reverting to alpha-5): > ... >>>> $ mingw-get upgrade mingw-get >>>> Load catalogue: ... >>>> Load catalogue: .../var/lib/mingw-get/data/mingw32-mingw-get.xml >>>> Load catalogue: ... >>>> upgrade: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz >>>> removing mingw-get-0.1-mingw32-alpha-5-bin.tar.gz >>>> upgrade: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz >>>> removing mingw-get-0.1-mingw32-alpha-5-lic.tar.gz > I see a small -- or maybe not so small -- anomaly there; I would > normally expect to see: > > $ mingw-get upgrade mingw-get > ... > Load catalogue: .../var/lib/mingw-get/data/msys-system-builder.xml > downloading: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz: 218013 b > downloading: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz: 16974 b > upgrade: mingw-get-0.1-mingw32-alpha-5.1-bin.tar.gz > removing mingw-get-0.1-mingw32-alpha-5-bin.tar.gz > upgrade: mingw-get-0.1-mingw32-alpha-5.1-lic.tar.gz > removing mingw-get-0.1-mingw32-alpha-5-lic.tar.gz > > Notice that the "downloading" messages were missing from Friday's > transcript; that's because the two requisite tarballs were already > present in my c:/MinGW/var/cache/mingw-get/packages directory. > >> I haven't looked through the source code but I was wondering if >> generating the debug build of mingw-get-alpha-5 and stepping through >> might help. > It might; working from CVS trunk might be even more profitable. > > Does it magically start working for you, if you pre-seed the package > cache with the two requisite tarballs, manually downloaded? Nope. Manually downloading the two tarballs to /var/cache/mingw-get/packages makes no difference, at least on my office machine. The upgrade still fails. > (I assume > that you have verified that they are called out from the catalogue file > in c:/MinGW/var/lib/mingw-get/data on each machine). Yes. I have checked the ...mingw-get.xml files are listing ...-alpha-5.1, both bin and lic files. > There have been > other reports of "incorrectly" configured[1] authenticating proxies > causing mingw-get to silently fail to download files; if a manual > download works around the issue for you, that tends to confirm that > we need to devote priority attention to this issue. > > [1] I use "incorrectly" configured here, in the sense that the proxy > does not interoperate with a Windows domain as Microsoft intend; I do > not mean to imply that this is necessarily a bad configuration. > |
From: Peter R. <p.r...@sh...> - 2011-02-14 15:44:20
|
On 14/02/11 15:09, Keith Marshall wrote: > On 14 February 2011 13:39, Peter Rockett wrote: >> On 14/02/11 12:55, Chris Sutcliffe wrote: >>> On 14 February 2011 06:12, Peter Rockett wrote: >>>> I have now tried this on three different machines at work. Same result: >>>> the upgrade fails (silently) on all three. All 3 machines are the >>>> nominally the same as my home machine. >>> I had the same issue and got around it by: >>> >>> mingw-get install mingw-get >>> >>> Chris >>> >> Sure, that fix occurred to me but the 'upgrade' path _should_ work. > To be pedantic, why would you think that when 'mingw-get --help' tells > you that the 'upgrade' function hasn't been implemented yet? Oh! Hadn't looked at that... > That said, it has actually been *partially* implemented, and I would > expect, in the present situation, that 'mingw-get upgrade' would behave > just the same as 'mingw-get install' >> Interesting that you have the same problem though. Are you downloading >> via broadband or a corporate LAN? > If it is a proxy/download issue, as I currently suspect, then I would > not expect 'mingw-get install' to succeed any more reliably than we see > with 'mingw-get upgrade'. That's why I've asked you to try the manual > download, to pre-seed the package cache. > See my earlier email re: pre-seeding. In the meantime, I have run 'mingw-get install mingw-get' on one of the other machines on which the upgrade failed silently earlier today. It works! (NB - No pre-seeding necessary.) 'mingw-get -v' now reports version 5.1. So it seems to work with the install option but not upgrade... P. |