Can't build Chromium on Windows, issue with boringssl

442 views
Skip to first unread message

Josh

unread,
Apr 6, 2016, 9:08:50 PM4/6/16
to Chromium-dev
Here's what I get when trying to build:

E:\workspace\chromium\src>ninja -C out\Debug chrome
ninja: Entering directory `out\Debug'
ninja: error: '../../third_party/boringssl/win-x86/crypto/poly1305/poly1305-x86.asm', needed by 'gen/third_party/boringssl/poly1305-x86.obj', missing and no known rule to make it

The src\third_party\boringssl\win-x86\crypto directory exists, but there's no poly1305 in there.

I tried a git pull in boringssl, which created a poly1305 directory, but no poly1305-x86.asm inside of it.

Guessing I'm missing something?

thanks,
-josh

Yoshisato Yanagisawa

unread,
Apr 6, 2016, 9:16:46 PM4/6/16
to jo...@stimulant.com, Chromium-dev
Did you execute "gclient sync" after you "git pull" src?
It looks like third_party/boringssl/boringssl.gypi (under control of chromium's src) is updated but third_party/boringssl/src seems not.

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

Josh Santangelo

unread,
Apr 6, 2016, 9:42:58 PM4/6/16
to Yoshisato Yanagisawa, Chromium-dev
That seemed to do it… thank you!
-- 
S T I M U L Λ N T
Josh Santangelo, Technical Director
P 415 363 0336 / HQ 415 255 7081 / T @stimulant

Josh Santangelo

unread,
Apr 6, 2016, 11:37:45 PM4/6/16
to Yoshisato Yanagisawa, Chromium-dev
Hm, maybe not… some other boringssl problem came up eventually.

E:\workspace\chromium\src>ninja -C out\Release chrome
ninja: Entering directory `out\Release'
[5658/21478] RULE Assembling nacl_swit...x86_64.gen\nacl_switch_unwind_win.obj.
 Assembling: nacl_switch_unwind_win.asm
[19655/21478] LINK_EMBED(DLL) chrome_child.dll
FAILED: E:\workspace\depot_tools\python276_bin\python.exe gyp-win-tool link-with
-manifests environment.x86 True chrome_child.dll "E:\workspace\depot_tools\pytho
n276_bin\python.exe gyp-win-tool link-wrapper environment.x86 False link.exe /no
logo /IMPLIB:chrome_child.dll.lib /DLL /OUT:chrome_child.dll @chrome_child.dll.r
sp" 2 mt.exe rc.exe "obj\chrome\chrome_child_dll.chrome_child.dll.intermediate.m
anifest" obj\chrome\chrome_child_dll.chrome_child.dll.generated.manifest
boringssl.lib(boringssl.err.obj) : error LNK2001: unresolved external symbol _kO
penSSLReasonValues
boringssl.lib(boringssl.err.obj) : error LNK2001: unresolved external symbol _kO
penSSLReasonValuesLen
boringssl.lib(boringssl.err.obj) : error LNK2001: unresolved external symbol _kO
penSSLReasonStringData
obj\skia\skia_opts_avx.lib : fatal error LNK1107: invalid or corrupt file: canno
t read at 0x750
Traceback (most recent call last):
  File "gyp-win-tool", line 315, in <module>
    sys.exit(main(sys.argv[1:]))
  File "gyp-win-tool", line 29, in main
    exit_code = executor.Dispatch(args)
  File "gyp-win-tool", line 71, in Dispatch
    return getattr(self, method)(*args[1:])
  File "gyp-win-tool", line 171, in ExecLinkWithManifests
    subprocess.check_call(ldcmd + add_to_ld)
  File "E:\workspace\depot_tools\python276_bin\lib\subprocess.py", line 540, in
check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'E:\workspace\depot_tools\python276_bin\p
ython.exe gyp-win-tool link-wrapper environment.x86 False link.exe /nologo /IMPL
IB:chrome_child.dll.lib /DLL /OUT:chrome_child.dll @chrome_child.dll.rsp chrome_
child.dll.manifest.res' returned non-zero exit status 1107
[19655/21478] CXX obj\chrome\browser\w...ensions.update_shortcut_worker_win.obj
ninja: build stopped: subcommand failed.

David Benjamin

unread,
Apr 7, 2016, 12:36:45 AM4/7/16
to jo...@stimulant.com, Yoshisato Yanagisawa, Chromium-dev
Those symbols come from third_party/boringssl/err_data.c which is generated on DEPS rolls. Are you perhaps missing it for some reason? I did just do a BoringSSL roll, but it didn't touch that file anyway.

---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

Josh Santangelo

unread,
Apr 7, 2016, 2:24:19 PM4/7/16
to David Benjamin, Yoshisato Yanagisawa, Chromium-dev
I only understand a couple of words of that… but I started from scratch and followed the directions a little more closely, and got it to build. Sorry for the noise.
Reply all
Reply to author
Forward
0 new messages