X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4B59EDB5.8020201@gmail.com>
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> 	 <4B59EDB5 DOT 8020201 AT gmail DOT com>
Date: Sat, 23 Jan 2010 01:13:25 +0100
Message-ID: <7f95d3561001221613ld403301w163993fbac99beaf@mail.gmail.com>
Subject: Re: Design issue with new MS-DOS style path warning?
From: Eric Vautier <eric.vautier+cygwin AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Tried "bash", "-x", "bash build.sh", "bash -x build.sh", forward
slashes in Windows environment variables, to no avail. But thank you
for your time and patience, Dave!
-e

On Fri, Jan 22, 2010 at 7:25 PM, Dave Korn
<dave DOT korn DOT cygwin AT googlemail DOT com> wrote:
> On 22/01/2010 17:55, Eric Vautier wrote:
>> 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.
>
> =A0That shell script presumably does some stuff first before invoking it;=
 maybe
> that's where the problem originates. =A0Also, you're running it from "sh"=
 in
> that situation, instead of "bash" as you do from the command-line; that m=
ight
> be relevant or might not. =A0("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.
>
> =A0Adding "-x" flag to the shebang might help.
>
>>> =A0 =A0 =A0<property name=3D"common" location=3D"${env.APP4_COMMON_ROOT=
}" />
>>> =A0 =A0 =A0<property name=3D"common-jar" value=3D"${common}/target/Comm=
on.jar" />
>
>>> APP4_COMMON_ROOT =3D C:\dev\prj\app4\Common
>
> =A0Try not using mixed slashes. =A0Both Cygwin and DOS should be fairly h=
appy with
>
> APP4_COMMON_ROOT =3D C:/dev/prj/app4/Common

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