New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 10 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2013
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

issue 8606

Sign in to add a comment

Issue 175301: Win64 linker errors in nacl target

Reported by, Feb 9 2013 Project Member

Issue description

Command line is: ninja -C out\Debug_x64 nacl
gyp settings:
GYP_DEFINES=component=shared_library target_arch=x64

I'm getting a spew of __imp_* symbol not found errors, where * is a Windows API function. I haven't dug into it at all, but I figured I'd cast a wider net to see if there's an easy answer.

Comment 1 by, Feb 9 2013

Blocking: chromium:8606

Comment 2 by, Feb 14 2013

Labels: Feature-Plugins-Pepper
I had a chance to take abother look and the offending target is actually ppGoogleNaClPluginChrome. I've attached the build log I get running: ninja -vC out\Debug_x64 ppGoogleNaClPluginChrome

My only guess here is that we're passing the wrong lib type (ia32 vs. x64) or something along those lines in one of the build files.
20.7 KB View Download

Comment 3 by, Feb 14 2013

Randomly adding @bbudge from the pepper team since this seems to be specific to the NaCl plugin.

Comment 4 by, Feb 14 2013


Comment 5 by, Feb 14 2013

Justin actually intended to build with:


building with GYP_DEFINES=component=shared_library actually works fine.

Comment 6 by, Feb 14 2013

I can't reproduce the issue with either a shared or static library build. I could be missing something though...

Comment 7 by, Feb 16 2013

Okay, my guess is that I'm the only one with a src-internal checkout, meaning I have platform SDK files under third-party. Since you don't have those directories present, your x64 build doesn't get its dependencies squashed by the ia32 AdditionalLibraryDirectories in native_client/build/common.gypi. If I remove those AdditionalLibraryDirectories entries, my build gets past the linking errors.

So, can I just remove those entries from common.gypi and rely on config.gypi to pick up the right ones for a NaCl standalone build? Because Chrome's common.gypi does the right architecture switch (if the settings don't get squashed).

Comment 8 by, Feb 22 2013

Status: Fixed
NaCl rolled forward and this is fixed. Only one build error left in NaCl for all targets.

Comment 9 by, Mar 10 2013

Project Member
Labels: -Area-Internals -Feature-NaCl -Feature-Plugins-Pepper Cr-Platform-NaCl Cr-Internals Cr-Content-Plugins-Pepper

Comment 10 by, Apr 5 2013

Project Member
Labels: Cr-Blink

Comment 11 by, Apr 6 2013

Project Member
Labels: Cr-Internals-Plugins

Comment 12 by, Apr 6 2013

Project Member
Labels: -Cr-Content-Plugins-Pepper Cr-Internals-Plugins-Pepper

Sign in to add a comment