#22 install-info.exe in gnuwin32\bin is 0 bytes

[austinian]

This seems to be a first run issue.
I downloaded 0.6.3 today, ran it, used download.bat to update, then used install.bat to install. (Used C:\gnuwin32 as the install path). After the supplemental install completed, install.exe and install-info.exe were both just empty files (inside the gnuwin32\bin directory), which lead to errors when install.bat tried to use install-info.exe. I deleted install.exe and install-info.exe and ran install.bat again and it ran correctly that time.
Using Windows XP Pro x64.

[Jay Satiro]

What directory is the GetGnuWin32 downloader in?

[Scott]

I experienced the same problem using Windows 7 x64 Home. Assuming the "downloader" is download.bat, it was at C:\scott\GetGnuWin32, and the installation was in C:\scott\GetGnuWin32 \gnuwin32. The same remedy worked for me.

[Jay Satiro]

Can you check C:\scott\GetGnuWin32\bin for 0 sized patch.exe, install.exe, install-info.exe? How did you invoke the installation? Did you run
install.bat
or
install.bat c:\scott\getgnuwin32\gnuwin32

[Scott]

I'll have to go home to check patch.exe, but install.exe, install-info.exe were both size 0 on the first installation attempt--just as autinian described. After deleting install*.exe and rerunning install.bat, they were no longer size 0 and the installation worked. The error message on the first installation was something like "install-info.exe is not a valid Windows application".

I ran "install.bat" with no arguments.

[Jay Satiro]

Another user has reported this issue via e-mail and it appears what happened in that case was he unzipped the GetGnuWin32 downloader to an already existing GnuWin32 directory, and then installed in GetGnuWin32, so that he ended up with a folder path like this:
C:\Program Files\GnuWin32\GetGnuWin32\gnuwin32

[kidmuto]

this will happen if the texinfo package is excluded (or fails during download/installation). similar issues may occur if patch and/or coreutils are excluded.

as part of the UAC workaround , install.bat runs a touch on patch.exe, install.exe, and install-info.exe after creating the relevant manifest files (but it doesn't check to make sure they exist first). if they weren't there to begin with, they will be created as zero byte files.

[Jay Satiro]

Thanks for your report. This project survives for legacy purposes and further maintenance is limited. I acknowledge this is a bug but it's too much of a corner case to work on. I'm closing as wontfix.