MIME-Version: 1.0
In-Reply-To: <4C648E6C.5070705@ntlworld.com>
References: <4C648E6C.5070705@ntlworld.com>
Date: Fri, 13 Aug 2010 09:29:29 -0600
Message-ID: <AANLkTin9pQdyjbpVtxWWeoV6mVnPFpgVpW3fuajosGNb@mail.gmail.com>
Subject: Re: bash postinstall script returns an error
From: Jeremy Ramer <jdramer@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Thu, Aug 12, 2010 at 6:14 PM,  <cy.20.superconductor@xoxy.net> wrote:
> 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 =A0|| ln -s /proc/self/fd/0 /dev/stdin =A0|| resu=
lt=3D1
>
> 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 wh=
en
> 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, b=
ut
> it still runs fine when done manually.

I saw the exact same results. I didn't mention it in the other thread
because the error didn't occur on manual run.

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