Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.2.0.14.0.20041129151309.046bfba0@pop.prospeed.net> Date: Mon, 29 Nov 2004 15:18:05 -0500 To: David Hinds , Cygwin List From: Larry Hall Subject: Re: A vexing installation problem In-Reply-To: <20041129195946.GA4932@sonic.net> References: <20041129071451 DOT GA15469 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129115158 DOT 046c9120 AT pop DOT prospeed DOT net> <20041129184442 DOT GA30302 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129135305 DOT 046bca10 AT pop DOT prospeed DOT net> <20041129195946 DOT GA4932 AT sonic DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:59 PM 11/29/2004, you wrote: >The postinstall scripts are all cygwin shell scripts and thus require >a functional 'sh' to do anything. And, as with all other cygwin >programs, 'sh' just exits without doing anything. Yep, so I'd recommend starting there. Check the Windows properties here to see who owns the file and who has permissions to execute it, etc. Also, you could do a strace on 'sh' to see if anything interesting shows up from that. Hopefully you'll see something interesting as a result. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/