Message-ID: <4C648E6C.5070705@ntlworld.com>
Date: Fri, 13 Aug 2010 01:14:36 +0100
From:  cy.20.superconductor@xoxy.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To:  cygwin@cygwin.com
Subject: bash postinstall script returns an error
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

I was going to mention passwd-grp.sh, but I see there's already a thread 
for that, so I'll move right on to the next one.

When I run setup.exe I always get an error for the bash.sh postinstall 
script, it seems to be on the line of:

/bin/test -e /dev/stdin  || ln -s /proc/self/fd/0 /dev/stdin  || result=1

I'm not so clear as to why this fails. test returns a status of 1 when 
the script is run by the installer, and yet /dev/stdin does exist. 
setup.log.full contains a predictable "ln: creating symbolic link 
`/dev/stdin': File exists".

If I run the postinstall script manually, test gives a status of 0, 
stdin is left alone and the script runs to the end successfully - it 
only fails when run from inside the installer (2.712) for me. I've tried 
invoking bash for the script using the same switches as those reported 
in setup.log.full, but it still runs fine when done manually.

If I remove /dev/stdin /dev/stdout and /dev/stderr the installer runs 
through fine.

The result isn't a big problem since the files exist, but it does seem odd.

Paul


--
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