preventing setup from forking

[Jason Pyeron]

> -----Original Message-----
> From: Jon Turney 
> Sent: Monday, May 17, 2021 4:41 PM
> 
> On 17/05/2021 20:59, Jason Pyeron wrote:
> > When I run
> >
> > c:\inst\setup-x86_64.exe -q -f -R c:\cygwin64 -l c:\inst -P libgcrypt-
> devel,asciidoc,cygport,gcc-g++,libpoppler-cpp-devel,libpcre-devel,dejagnu,texlive-
> collection-latex
> >
> > or
> >
> > c:\inst\setup-x86_64.exe -qvW -f -R c:\cygwin64 -l c:\inst -P libgcrypt-
> devel,asciidoc,cygport,gcc-g++,libpoppler-cpp-devel,libpcre-devel,dejagnu,texlive-
> collection-latex
> >
> > the prompt returns immediately. This is causing problems when it is run from a (windows)
> ssh session.
> 
> --wait should be doing what you want.

-W is the same, no impact.

> 
> I recently discovered that if the invoking shell is PowerShell, then
> because setup is a GUI application, PowerShell doesn't wait, so maybe
> that's what's happening here...
> 

Fits my observations. https://superuser.com/questions/908664/have-the-command-prompt-launch-an-application-like-notepad-and-block-until-it-is helps.

start /b /wait c:\inst\setup-x86_64.exe -q -f -R c:\cygwin64 -l c:\inst -P libgcrypt-devel,asciidoc,cygport,gcc-g++,libpoppler-cpp-devel,libpcre-devel,dejagnu,texlive-collection-latex

from cmd.exe use start /b /wait

/B Start application without creating a new window. The application has ^C handling ignored. Unless the application enables ^C processing, ^Break is the only way to interrupt the application.

/WAIT Start application and wait for it to terminate.

My real issue was the user was not an admin - doh!