Re: cygwin make fails when calling mkdir in Windows 7
On 2013-01-04 16:34Z, cpow wrote: [...] > 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. Judging from the error message in your original post: make[1]: *** No rule to make target ``, needed by ``. Stop. it doesn't sound like 'mkdir' is failing--rather, it sounds like 'make' can't figure out what command is needed to create 'path'. Can you post the rule that's intended to do that? -- 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
Re: cygwin make fails when calling mkdir in Windows 7
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
Re: cygwin make fails when calling mkdir in Windows 7
On Fri, Jan 4, 2013 at 11:02 AM, David Stacey wrote: > On 03/01/13 22:49, Warren Young wrote: >> >> If this were affecting everyone, you'd be seeing a lot of yelling on this >> list. (More than normal I mean. :) ) Those of us who maintain Cygwin >> packages would all be affected, for instance. > > > I may have run into this problem earlier in the week - I wanted to rebuild > Subversion to test Warren's latest sqlite3 build. I had 'make' fail a couple > of times when creating directories, but didn't give it too much thought - I > just put it down to anti-virus software getting in the way. > Word of caution: Anti-virus software can cause ill results during the configure process if it is opening files as they are being created to scan them. You should tell the anti-virus software to ignore your work directory. I myself have a NAT disk that I tell my anti-virus to not scan that disk during the automated scan. > BTW, I was running good old 32-bit WinXP Pro SP3. > It doesn't matter which OS, the anti-virus is a bad thing for configure and make. -- Earnie -- https://sites.google.com/site/earnieboyd -- 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
Re: cygwin make fails when calling mkdir in Windows 7
On 03/01/13 22:49, Warren Young wrote: If this were affecting everyone, you'd be seeing a lot of yelling on this list. (More than normal I mean. :) ) Those of us who maintain Cygwin packages would all be affected, for instance. I may have run into this problem earlier in the week - I wanted to rebuild Subversion to test Warren's latest sqlite3 build. I had 'make' fail a couple of times when creating directories, but didn't give it too much thought - I just put it down to anti-virus software getting in the way. BTW, I was running good old 32-bit WinXP Pro SP3. Dave. -- 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
Re: cygwin make fails when calling mkdir in Windows 7
On 1/3/2013 14:50, cpow wrote: cygwin1.dll version is 1.7.13. Is there a particularly good reason you haven't tried upgrading yet? Not that I have any specific reason to believe there is a fix in the past three versions you have skipped, but it shows a willingness to help diagnose it on your part, and ensures those who might help are on the same page with you. You can't expect people to downgrade just to help you, if it turns out to be an old bug. The other standard bit of advice, at the bottom of every post to this list, is "Problem reports: http://cygwin.com/problems.html"; and are not terribly relevant but is under /cygdrive/c/... What happens if you move the build tree under ~cpow? Does it always succeed, or does the problem remain? I've found elsewhere such as running Cygwin as "administrator" and making sure I have local administrator rights on my laptop--which I do. This suggests BLODA. Nothing other than some bit of quasi-malware should have the ability to deny Administrator the right to do anything. Executing: mkdir -pv after the make failure and re-issuing the make command causes the build to progress past the point of this fault, as expected. 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? 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. Soon, though, it stumbles when trying to create another path. Is it always the same paths, or is it random? I'd really like to know if there's a solution to this problem other than having to manually mkdir the paths that make seems to fail to be able to make. It slows down my automated build quite dramatically! If this were affecting everyone, you'd be seeing a lot of yelling on this list. (More than normal I mean. :) ) Those of us who maintain Cygwin packages would all be affected, for instance. -- 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
cygwin make fails when calling mkdir in Windows 7
I'm using make package version 3.82.90-1. cygwin1.dll version is 1.7.13. Occasionally make will fail with the error: make[1]: *** No rule to make target ``, needed by ``. Stop. and are not terribly relevant but is under /cygdrive/c/... I started having this problem on upgrading to Windows 7. I've tried the "solutions" I've found elsewhere such as running Cygwin as "administrator" and making sure I have local administrator rights on my laptop--which I do. However, I still have this problem. Executing: mkdir -pv after the make failure and re-issuing the make command causes the build to progress past the point of this fault, as expected. Soon, though, it stumbles when trying to create another path. Interestingly make doesn't seem to fail when creating the first level of a path hierarchy. For example, if the makefile were trying to create: folder1 folder1/subfolder1 folder1/subfolder2 folder1 is created but the errors occur when it hits the rule trying to create the subfolderN's. ls -al shows the permissions for folder1 and subfolder1 are identical even though one was created by make and one was created by me with mkdir: drwxr-xr-x+ 1 e198614Domain Users 0 Jan 3 15:45 I'd really like to know if there's a solution to this problem other than having to manually mkdir the paths that make seems to fail to be able to make. It slows down my automated build quite dramatically! -- View this message in context: http://cygwin.1069669.n5.nabble.com/cygwin-make-fails-when-calling-mkdir-in-Windows-7-tp95185.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
