MSB6006 error code 53

[pdwiki]

I setup a new laptop today with Windows 8, VS 2010 Ultimate and all the other requirements to build Chromium. I used the following .gclient file to checkout Chromium last night:

solutions = [

  { "name"        : "src",

    "url"         : "https://src.chromium.org/chrome/trunk/src",

    "custom_deps" : {

      "src/content/test/data/layout_tests/LayoutTests": None,

      "src/chrome_frame/tools/test/reference_build/chrome_win": None,

      "src/chrome/test/data/perf/canvas_bench": None,

      "src/chrome/test/data/perf/frame_rate/content": None,

      "src/chrome/tools/test/reference_build/chrome_mac": None,

      "src/chrome/tools/test/reference_build/chrome_win": None,

      "src/chrome/tools/test/reference_build/chrome_linux": None,

      "src/third_party/hunspell_dictionaries": None,

    },

    "safesync_url" : "https://chromium-status.appspot.com/lkgr"

  }

]

Now, every time I am building Chromium, I am getting a MSB6006 error with code 53. This is happening in the generate_files project in yasm and in turn causing other projects to fail. Below is the error message:

1>------ Build started: Project: generate_files, Configuration: Debug Win32 ------

1>Build started 5/18/2013 5:02:05 PM.

1>InitializeBuildStatus:

1>  Touching "..\..\build\Debug\obj\generate_files\generate_files.unsuccessfulbuild".

1>CustomBuild:

1>  Running source/patched-yasm/modules/arch/x86/gen_x86_insn.py.

1>  Generating yasm version file: ..\..\build\Debug\obj/global_intermediate/third_party/yasm/version.mac.

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(151,5): error MSB6006: "cmd.exe" exited with code 53.

1>

1>Build FAILED.

1>

1>Time Elapsed 00:00:02.02

========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Any idea what is causing this? The Chromium checkout I have from 3-4 days back on a different computer is working perfectly. I see that the waterfall is showing red but my checkout should be the last green stable version I think.

Any help will be greatly appreciated! Thanks.

[Scott Graham]

Error code 53 is "The network path was not found". Maybe you've done some remapping or something that's stale now?

Otherwise, you could try turning up the verbosity of MSBuild or trying the ninja build.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
 
 
 

[pdwiki]

Thanks for the reply. I always checkout the code and run a build first before making any changes. Touched absolutely nothing!

Attached is the detailed log file from VS. I see a file is missing but am having trouble why this is happening. Any ideas?

Thanks again.

[Scott Graham]

I'd guess based on the command line and the error level that it's probably a cygwin<->win32 style path problem (\\ being interpreted as a network path). But I don't see anything obviously wrong.

I would try to run those commands standalone to see if either run outside msbuild or give a more useful error message. Then you can add prints to the scripts to see what's going wrong.

[pdwiki]

I thought I would give ninja a try and ran into the MSVCP100d.dll missing error. Do I have to set the "Runtime Library" setting to Multi threaded Debug (/MTd) for this?

[pdwiki]

I made some progress in finding what is going wrong. The generate_files project fails to build when I turn on component build by placing a include.gypi file in the .gyp folder. If I remove the include.gypi file, all the projects build but the linker shows the following error:

LINK : fatal error LNK1210: exceeded internal ILK size limit; link with /INCREMENTAL:NO

And if I try building with Ninja, I get a MSVCP100d.dll missing error even though it exists in the system. I am running VS 2010 Ultimate on a Windows 8 laptop, with 8GB RAM.

Any ideas as to how at least 1 of the build processes can be made to work will be greatly appreciated!

[Trent Apted]

On 20 May 2013 08:48, pdwiki <praba...@gmail.com> wrote:

Any ideas as to how at least 1 of the build processes can be made to work will be greatly appreciated!

The Release build should work, to avoid that `ILK size limit` error that you get when building a non-component build.

Otherwise, perhaps try one of the other ways of turning on the component build:

 1. GYP_DEFINES=component=shared_library gclient runhooks

(or) 2. create a file in the same folder as your .gclient called `chromium.gyp_env`, with

{

  'GYP_DEFINES': 'component=shared_library',

}

(or) 3. edit build/common.gypi and change the line

      'component%': 'static_library',

to be

      'component%': 'shared_library',

I'd also recommend building with ninja. Export GYP_GENERATORS=ninja to your environment, or edit that chromium.gyp_env file to add a line:

  'GYP_GENERATORS': 'ninja',

Let us know how you go!

[Thiago Farina]

On Sun, May 19, 2013 at 9:27 PM, Trent Apted <tap...@chromium.org> wrote:
> The Release build should work, to avoid that `ILK size limit` error that you
> get when building a non-component build.
>
> Otherwise, perhaps try one of the other ways of turning on the component
> build:

You have a fourth option, ~/.gyp/include.gypi. Not sure if that works
on Windows though.

--
Thiago

[Alex Pakhunov]

You have a fourth option, ~/.gyp/include.gypi. Not sure if that works
on Windows though.

It does.

--

Alex.

[pdwiki]

Thanks for your suggestions. I tried all the options you suggested but it did not work. It sees like the only time component build is being detected is when I have a include.gypi folder in my user root in Windows 8 (e.g., C:\Users\<username>\.gyp\include.gypi). None of the options 1, 2 and 3 work for me. In all those cases, the linker does not detect component build. It keeps showing me the same error which is shown below:

452>     Creating library ..\build\Debug\lib\chrome_dll.lib and object ..\build\Debug\lib\chrome_dll.exp

452>LINK : fatal error LNK1210: exceeded internal ILK size limit; link with /INCREMENTAL:NO

The other option of building with Ninja is just not working for me. Everytime I try to build with ninja the project builds and at one point or the other it shows a "The program can't start because MSVCP100D.dll is missing from your computer." error. That file exists on my computer!  Attached is a screenshot of the error.

Is this all due to Windows 8? Do I have to do anything different to get ninja to compile Chromium? I am using the steps listed under the Windows section in this url -  https://code.google.com/p/chromium/wiki/NinjaBuild

If either ninja or the component build worked then it would be great. Unfortunately none work and I cannot do a release build for every minor change.

Any ideas what to try next or should I just format the laptop and setup everything again and hope it works?

[Trent Apted]

Did building in out/Release work?

another idea: http://www.chromium.org/developers/how-tos/build-instructions-windows#TOC-Automatic-simplified-toolchain-setup ;)

[pdwiki]

The out/Release build "seems" to be working. It is 50% done and I have not received any error yet. On all other occassions I got the error at 10% or so. Will let you know what happens.

One question - I was avoiding the toolchain setup as it says build will be possible only through ninja. How do I debug then? Using "devenv.com /debugexe chrome.exe"? Will I be able to see detailed error messages that way? I have never done it this way before...so wanted to know what I am getting myself into :)

[Trent Apted]

windbg does a decent job for debugging. Sawbuck ( https://code.google.com/p/sawbuck/ ) is another excellent tool, for reading log output. Drag the separator at the bottom of the window up, and you'll get a stacktrace when you click on a log line.

[pdwiki]

Release build using ninja worked fine! Will try the toolchain in 7-8 hours time...need some sleep now. I will let you know how it goes. Thanks for all the help till now.

[pdwiki]

The toolchain method worked but when I executed the debug version of Chromium then it gave me the msvcp100d.dll missing error again. I copy/pasted the file into the out/Debug directory and then it showed me that the msvcr100d.dll was missing. So I copied the msvcr100d.dll into the out/Debug directory too and then only the chrome.exe file executed properly.

I also built the release version and it worked fine without me having to copy/paste the 2 dll's into the release directory.

On Monday, May 20, 2013 1:11:33 AM UTC-6, tapted wrote: