Postinstall autorebase not working cleanly

Question

I always get an error when adding a package to cygwin, for example: Package: Unknown package autorebase.bat exit code 1

/var/log/setup.log.full indicates a problem:

2013/12/02 10:07:57 running: cmd.exe /c "C:\cygwin64\etc\postinstall\autorebase.bat" 2013/12/02 10:07:57 abnormal exit: exit code=1 

Running cmd.exe / c "C: \ cygwin \ etc \ postinstall \ autorebase.bat" complains that the dash was not found.

 C:\Users\xxx>cmd /c C:\cygwin64\etc\postinstall\autorebase.bat 'dash' is not recognized as an internal or external command, operable program or batch file. 

So, I changed autorebase.bat with

 @echo off rem Postinstall scripts are always started from the Cygwin root dir rem so we can just call dash from here path .\bin;%path% dash /bin/rebaseall -p 

to

 @echo off rem Postinstall scripts are always started from the Cygwin root dir rem so we can just call dash from here C: cd C:\cygwin64 path .\bin;%path% dash /bin/rebaseall -pv 

After this change, I can run cmd / c C: \ cygwin64 \ etc \ postinstall \ autorebase.bat purely from the command line, but the error still appears when I add the package using the installer.

How to fix it?

Answer 1

If this does not work, try downloading the 32-bit version. If you try to add gcc, g ++ is the same for 32 or 64. If you try to add Cygwin / Mingw, the 32-bit compiler works fine for a 64-bit machine (this is true for any application in any way)

Answer 2

This problem continues to evolve ... with complex (but non-working) solutions offered on all bulletin boards. A working solution is implied by https://cygwin.com/faq/faq.html#faq.using.bloda . Oddly enough, I do not find any specific direction on the connection between them from Cygwin.

As far as I understand, rebooting Cygwin (script 0p_000_autorebase.dash, which runs at the end of the setup) runs into problems because it stumbles on other things that you installed. Most likely one of your antivirus filters. One solution is to boot in Safe + Networking mode, install, reboot. Everything worked fine (at least for me).

This probably doesn't help the installation folders get the read-only flag (although I'm not quite sure why this matters if you use the setting in admin mode, but I might be missing something).