I have Update 2 installed. http://www.microsoft.com/en-us/download/details.aspx?id=38188
Sent from my iPad
On May 6, 2013, at 7:29 PM, Ben Reser <ben_at_reser.org> wrote:
> On Mon, May 6, 2013 at 3:40 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>> I like that the script can be re-run.
>
> Yes, I tried to make it smart enough to avoid redoing work that was
> already done.
>
>> The script then started chugging along and building. It looks like it
>> failed at the end of building httpd. Not really sure why or what is
>> wrong:
>>
>> ========== Build: 7 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
>> ========== Build: 118 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0
>> \Common7\IDE\devenv.COM"' : return code '0x1'
>> Stop.
>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0
>> \VC\BIN\nmake.exe"' : return code '0x2'
>> Stop.
>> Failed building/installing httpd/apr/apu/api (exit code: 512) at build-svn-deps-
>> win.pl line 245.
>>
>> Any ideas? I searched the output for what Failed and do not see
>> anything referenced.
>>
>> Searching for all instanced of "Error". It might be this:
>>
>> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.ta
>> rgets(347,5): error MSB6003: The specified task executable "CL.exe" could not be
>> run. The process cannot access the file 'C:\SVN\deps-1.8.x\build\httpd\modules\
>> proxy\balancers\Release\cl.write.1.tlog' because it is being used by another pro
>> cess.
>
> The above error is a bug in the httpd build process related to newer
> versions of Visual Studio. Since everything shares the same
> intermediate directories concurrent builds start blowing up over this
> log file. The correct fix for this is to use different intermediate
> build directories for each module. This is a major change to the
> httpd build system so I didn't do it. Rather I applied a workaround
> by setting a flag that tells Visual Studio not to use the files that
> create the problem.
>
> Let me see if I can reproduce this on my end.
>
> What's the exact version of Visual Studio 2012 that you're using? I'm
> on 11.0.50727.1. I haven't bothered to apply the updates to it.
Received on 2013-05-07 01:48:10 CEST