X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4B59EDB5.8020201@gmail.com>
Date: Fri, 22 Jan 2010 18:25:57 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Design issue with new MS-DOS style path warning?
References: <81D39E818991E549B1F66EB6A7D18422BE8626 AT AVSMOEXCL02 DOT activision DOT com> 	 <4B57DF25 DOT 4040605 AT gmail DOT com> 	 <7f95d3561001220517k4fd93c6btdda02fd06596e97f AT mail DOT gmail DOT com> 	 <20100122154551 DOT GB4020 AT ednor DOT casa DOT cgf DOT cx> 	 <7f95d3561001220823md77as48d8128d396c8370 AT mail DOT gmail DOT com> 	 <4B59D9FC DOT 3070307 AT gmail DOT com> 	 <7f95d3561001220923i60a15fe6u71c36b0baeda3ebe AT mail DOT gmail DOT com> 	 <4B59E4B2 DOT 3050001 AT gmail DOT com> <7f95d3561001220955r1c79df20xe76755160a4e32bc AT mail DOT gmail DOT com>
In-Reply-To: <7f95d3561001220955r1c79df20xe76755160a4e32bc@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 22/01/2010 17:55, Eric Vautier wrote:
>>  So, you are lumbered with some massive mish-mash of complex build scripts,
>> ANT, java, mixture of cygwin and native executables and god knows what else,
>> and somewhere down in the middle of it something's invoking what it probably
>> expects to be a win32 program and getting the cygwin version, or vice-versa.
>> Ouch.  You're going to have to figure out what's going on way down in the
>> internals and try and extract a simple testcase.
> 
> Yes, it's a slightly complicated build script, but it does the job
> properly when invoked manually. It only fails if it is invoked from
> inside a wrapping shell script.

  That shell script presumably does some stuff first before invoking it; maybe
that's where the problem originates.  Also, you're running it from "sh" in
that situation, instead of "bash" as you do from the command-line; that might
be relevant or might not.  ("sh" is an alias for "bash" that invokes it with
slightly-altered behaviour.)

> To sum up: all 5 builds (three maven, two ant) work fine when invoked
> manually from the command-line. The two ant builds fail in the overall
> build invocator (build.sh, but I should probably call it
> build-all.sh), whose sole task is to launch the 5 builds from inside
> their own directories; the three maven builds are fine.
> 
> I see no reason why calling that ant build from inside a shell script
> should mess up the paths with C:\cygdrive\c\dev\ prefixes. build.sh
> does have #!/bin/sh at the top. Will investigate a little more.

  Adding "-x" flag to the shebang might help.

>> 	<property name="common" location="${env.APP4_COMMON_ROOT}" />
>> 	<property name="common-jar" value="${common}/target/Common.jar" />

>> APP4_COMMON_ROOT = C:\dev\prj\app4\Common

  Try not using mixed slashes.  Both Cygwin and DOS should be fairly happy with

APP4_COMMON_ROOT = C:/dev/prj/app4/Common

    cheers,
      DaveK


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