Installer of Cygwin 64 seems to freeze when executing /etc/postinstall/xlaunch.sh - version 2.874

[Jon Turney]

On 03/06/2016 16:26, Jean-Paul Bouchet wrote:
> May be is the value of PATH the problem?
> When I launch, by a double click on the bash.exe file, a cygwin bash
> shell (C:\cygwin64\bin\bash.exe) and I display $PATH, I don't find any
> cygwin directory in the list, but a list of windows directories:
> /cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:
> ...

As Ken Brown has explained, double-clicking bash.exe does not set the PATH.

You should run it from the "Cygwin Terminal" shortcut, which starts a 
login shell, which reads profile scripts, which set the PATH appropriately.

> So, when I execute in the cygwin bash shell  the command '/bin/sh -x
> /etc/postinstall/xlaunch.sh.done', I get the same errors than those I
> get when I execute 'C:\cygwin64\bin\sh -x
> /etc/postinstall/xlaunch.sh.done' in the windows command interpreter:
> the command 'uname' is unknown.
>
> If I change the value of PATH with PATH=/cygdrive/c/cygwin64/bin:$PATH
> and export PATH, the execution of 'sh -x
> /etc/postinstall/xlaunch.sh.done' don't give any errors.
>
> What is the value of PATH when the installation executes the set of
> postinstall scripts ?

setup cleans the PATH to start with '/bin:/usr/sbin:/sbin', and contain 
any directories in the existing PATH which start with the windows system 
directory (e.g. '/cygdrive/cWindows/System32')

Again, having an incorrect PATH doesn't reproduce the problem of the 
script freezing, so I don't think this is the underlying cause of the 
problem you see.

> On 03/06/2016 14:41, Jon Turney wrote:
>> On 02/06/2016 17:22, Jean-Paul Bouchet wrote:
>>> Please find attached the script /etc/postinstall/xlaunch.sh and the
>>> output of its execution (file postinstall_xlaunch.txt).
>>
>> Thanks.
>>
>> I guess this doesn't reproduce the problem (freezing), as this is just
>> what I would expect to see when running the script without the PATH set?
>>
>> Perhaps you could try again from a cygwin bash shell?

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple