From: Robert Klemme Date: 2012-02-22T07:35:12+09:00 Subject: Re: Compile 1.9.3 on cygwin On Tue, Feb 21, 2012 at 6:33 PM, Jon Forums wrote: >> I finally found out what went wrong: apparently McAfee AV interfered >> with the build process and prevented execution. >> >> ...SNIP... >> >> Description translated means something like: "Would be blocked by >> access control rule (rule is in warning mode). (Common - basic >> protection: prohibit execution of files in temp folder for common >> programs)." >> >> Despite the error message apparently execution _was_ blocked.  My fix >> was as easy as to provide a different temp dir: >> >> $ mkdir tmp >> $ TMP="$PWD/tmp" make install > > > Interesting, but I don't think this is the best way to go. For one, it's > one more manual step to remember even though you could easily write a > build script to automate. It's good enough for me (see below). > Many of today's AV's have the concept of "real-time protection" that can > cause havoc when you want to build from source. > > I've had similar issues when building MRI on Windows using (native) > MSYS/MinGW with or without the RubyInstaller build helper recipes. Once > I added the necessary dirs to my AV's real-time protection exclusion > list, issue solved. And at least with AVG the exclusion list survives > upgrades. > > Does McAfee have similar exclusion lists and does it solve your build > issue? I guess it does but for one I can't be bothered to go through the process with our corporate IT (policy control all over the place, we are not granted permission to edit settings) and the way they set up systems and second since the message indicates it is checking a temp dir taking the temp dir out of the list kind of defies the purpose of the rule. :-) Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/