X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Jake Subject: Re: cl.exe and a C1083 error Date: Thu, 6 Aug 2009 23:04:46 +0000 (UTC) Lines: 8 Message-ID: References: <4A7A5832 DOT 4090108 AT cygwin DOT com> <4A7B0B7C DOT 2020608 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes 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 > However, if I were to hazard a guess, I would surmise that the build machines > have the path you indicate at the root of the drive they run the build from (C: > perhaps?). You might That was the problem. On the server there was a c:\usr\local\build directory, on my system I mounted directories from completely different spots. When I moved it to c:\usr\local\build it worked perfectly. So really because ms understands the / they weren't using posix paths at all. Thanks for the help. -- 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