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: <4B59E4B2.3050001@gmail.com> Date: Fri, 22 Jan 2010 17:47:30 +0000 From: Dave Korn 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> In-Reply-To: <7f95d3561001220923i60a15fe6u71c36b0baeda3ebe@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: 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 On 22/01/2010 17:23, Eric Vautier wrote: > FYI, the "faulty but perfectly logical" path in one of the two > failures (I'll try to trace the other one as well) was arrived at > from: > > > 0. Invocation from sh build.sh (mid-script): > > ant clean get-common debug > > 1. Output of build script: > > AndroidApp > BUILD FAILED > C:\dev\prj\app4\AndroidApp\build.xml:343: Warning: Could not find file > C:\cygdrive\c\dev\prj\app4\Common\target\Common.jar to copy. > > 2. Build target (lines 342-344): > > > > > > 3. Properties: > > > > > 4. Environment variable: > > APP4_COMMON_ROOT = C:\dev\prj\app4\Common > > > Typing "ant clean get-common debug" works fine from the command line. 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. 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