X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,BAYES_05,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: sourceware.org Date: Fri, 4 Jan 2013 08:34:43 -0800 (PST) From: cpow To: cygwin AT cygwin DOT com Message-ID: <1357317283112-95208.post@n5.nabble.com> In-Reply-To: <50E60B10.2000804@etr-usa.com> References: <1357249850421-95185 DOT post AT n5 DOT nabble DOT com> <50E60B10 DOT 2000804 AT etr-usa DOT com> Subject: Re: cygwin make fails when calling mkdir in Windows 7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Warren Young wrote > Is there a particularly good reason you haven't tried upgrading yet? Yes. I am locked to that version for business reasons. I have started the conversation internally RE upgrading. Warren Young wrote > You can't expect people to downgrade just to help > you, if it turns out to be an old bug. I'm not expecting anyone to downgrade. Warren Young wrote > What happens if you move the build tree under ~cpow? Does it always > succeed, or does the problem remain? Apologies I meant to specify more of the path but forgot to paste! The location of my build is several folders under ~, where ~ is: $ echo $HOME /cygdrive/c/Projects The permissions of that: drwxrwxrwx+ 1 Administrators Domain Users 0 Dec 13 15:56 Projects Warren Young wrote > This suggests BLODA. Nothing other than some bit of quasi-malware > should have the ability to deny Administrator the right to do anything. Having googled BLODA I can assume you might be referring to McAfee or anything else my employer's overprotective IT department forces me to use? I have tried with McAfee's "on access scan" and "access protection" tasks disabled and get the same results. If I uninstall McAfee I'm likely to receive a nastygram from Big Brother. Warren Young wrote > What happens if you just re-start the make operation? Does it persist > in failing to get past that point, or does re-starting it sometimes get > you past the problem? If I restart the make operation without doing mkdir myself it fails in exactly the same spot. Restarting it without doing mkdir myself never gets past the problem. Warren Young wrote > I'm basing this question on the assumption that the Makefile is > well-written, such that if the directory creation fails, re-starting the > make operation will retry the mkdir operation. That requires that > someone has set up the necessary dependency rules, though. I've inspected the makefile and I think it is constructed well. Warren Young wrote > Is it always the same paths, or is it random? Same. -- View this message in context: http://cygwin.1069669.n5.nabble.com/cygwin-make-fails-when-calling-mkdir-in-Windows-7-tp95185p95208.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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