Re: iup news// iup4eu3
- Posted by jimcbrown (admin) Jul 26, 2016
- 2153 views
Does IUP really offer hope of being more functional than EuGTK on Windows? What is going on?
reference:
Regards, Ken
OK, thought I'd give it another go. Here's what happened:
I'm familiar with mingw and cygwin (which MSYS is based off of), so I might be able to help here.
I did not expect it to be this complicated though. Back in 2001 when I looked at it, you just grabbed a zip of the binaries off of a web site somewhere (for GTk 1.3) and everything worked.
Ran pacman -Sy pacman (+36MB), restarted msys2
Why this step, out of curiosity? It's not mentioned in https://blogs.gnome.org/nacho/2014/08/01/how-to-build-your-gtk-application-on-windows/
I wonder if the reason for the multiple cygwin1.dll(s) below is because of this, resulting in a only-partly upgraded msys2 or something. (Upgrade pacman requires newer cygwin1.dll but older msys2 requires the older cygwin1.dll)
Ran pacman -Su (+18MB), error with cygwin1.dll. Found 3, the most recent of which was 64-bit, so I renamed them all. msys2 would not start.
msys2 requires cygwin1.dll - not sure why you had three of them though. Something seems broken here (likely in msys2 itself) but if you had renamed two of three at a time, trying each cygwin1.dll in turn, you might have succeeded in getting it to run. (OTOH, you might not have.)
uninstalled msys2 completely, reinstalled. Ran pacman -Sy pacman (+36MB), restarted msys2 Ran pacman -Su (+18MB), error with cygwin1.dll. msys2 would not start.
So you repeated the same steps and got the same result. Not entirely unexpected.
Uninstalled msys2 completely, unrenamed the latest cygwin1.dll. Reinstallation failed.
The newer cygwin1.dll is likely not compatible with the older msys2 binaries that the installer was trying to run to install msys2. Hence the failure. (Or so I reckon, at least.)
Again, however, this does seem needlessly complicated....
I now have C:\msys32\home\Pete with no admin access, and no way to delete it. [Error Applying Security. Failed to enumerate objects in the container. Access is denied.]
Windoze brain-damage. Seriously. I believe (as a matter of faith) that people deserve to have stuff like this happen to them for using Windoze.
Oh well, I guess it'll have to wait until I next buy a new PC then.
That said, the easy way to get rid of it would be to grab a GNU/Linux LiveCD, reboot, and wipe out the directory from there.
If one wanted to insist on using Windoze to clean up (say because one was not in a position to reboot anytime in the near future, for example), there are some exoteric methods that can be tried. For example, try using a SYSTEM cmd prompt and running a deltree replacement ( https://www.raymond.cc/blog/deltree-command-replacement-in-windows-2000-or-windows-xp/ ). (And, to get a SYSTEM cmd prompt in the first place, http://stackoverflow.com/questions/77528/how-do-you-run-cmd-exe-under-the-local-system-account )
Other, simpler methods may also work: http://www.thewindowsclub.com/fix-failed-to-enumerate-objects-in-the-container https://answers.microsoft.com/en-us/windows/forum/windows_8-security/permission-error-failed-to-enumerate-objects-in/93ea883f-853f-4981-a697-928bfbc71642?page=2
