www/chromium build fails

[Volodymyr Kostyrko]

05.10.2012 15:32, Rene Ladan wrote:
>> I just tried to update chromium up to v22 and it fails with:
>>
>>    TOUCH
>> out/Release/obj.target/third_party/WebKit/Source/WebCore/WebCore.gyp/webcore_bindings_sources.stamp
>>
>>    AR(target) out/Release/obj.target/ui/surface/libsurface.a
>>    AR(target) out/Release/obj.target/gpu/libcommand_buffer_service.a
>>    AR(target) out/Release/obj.target/webkit/support/libwebkit_user_agent.a
>>    RULE
>> remoting_proto_chromotocol_gyp_chromotocol_proto_lib_target_genproto_0
>> out/Release/pyproto/remoting/proto/audio_pb2.py
>>    RULE
>> remoting_proto_chromotocol_gyp_chromotocol_proto_lib_target_genproto_1
>> out/Release/pyproto/remoting/proto/control_pb2.py
>>    RULE
>> remoting_proto_chromotocol_gyp_chromotocol_proto_lib_target_genproto_2
>> out/Release/pyproto/remoting/proto/event_pb2.py
>>    RULE
>> remoting_proto_chromotocol_gyp_chromotocol_proto_lib_target_genproto_3
>> out/Release/pyproto/remoting/proto/internal_pb2.py
>>    RULE
>> remoting_proto_chromotocol_gyp_chromotocol_proto_lib_target_genproto_4
>> out/Release/pyproto/remoting/proto/video_pb2.py
>>    RULE
>> third_party_libvpx_libvpx_gyp_gen_asm_offsets_target_obj_int_extract_0
>> out/Release/obj/gen/third_party/libvpx/asm_com_offsets.asm
>> Unable to open file: No such file or directory
>>
>> Building WITH CLANG, CODECS and GCONF. Mentioned file exists and is empty.
>>
>> # uname -a
>> FreeBSD ar1l0u 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r241156M: Wed
>> Oct  3 13:58:16 EEST 2012     arcade at ar1l0u:/usr/obj/usr/src/sys/MINIMAL
>>   amd64
>>
>> Modifications: tmpfs rbtree patch, zfs feats patch.
>>
>> World is built WITH_CLANG_IS_CC, WITH_LIBCPLUSPLUS, WITH_BSD_GREP.
>>
> Maybe this is caused by WITH_CLANG_IS_CC or WITH_LIBCPLUSPLUS ? Chromium
> should build fine with a vanilla CURRENT and its CLANG option.

I doubt it as www/chromium tend to use clang/clang++ not cc/c++. I also 
haven't changed CFLAGS to make use of LIBCPLUSPLUS.

I just don't know how can I correctly inspect what's going on. If I grep 
the build for 'vpx' I'll get:

   CC(target) 
out/Release/obj.target/libvpx_asm_offsets/third_party/libvpx/source/libvpx/vp8/common/asm_com_offsets.o
   CC(target) 
out/Release/obj.target/libvpx_asm_offsets/third_party/libvpx/source/libvpx/vp8/decoder/asm_dec_offsets.o
   CC(target) 
out/Release/obj.target/libvpx_asm_offsets/third_party/libvpx/source/libvpx/vp8/encoder/asm_enc_offsets.o
   CC(host) 
out/Release/obj.host/libvpx_obj_int_extract/third_party/libvpx/source/libvpx/build/make/obj_int_extract.o
   AR(target) out/Release/obj.target/third_party/libvpx/libvpx_asm_offsets.a
   LINK(host) out/Release/libvpx_obj_int_extract
   LINK(host) out/Release/libvpx_obj_int_extract: Finished
   ACTION 
third_party_libvpx_libvpx_gyp_gen_asm_offsets_target_unpack_lib_posix 
out/Release/obj.target/gen_asm_offsets/geni/asm_com_offsets.o
   RULE 
third_party_libvpx_libvpx_gyp_gen_asm_offsets_target_obj_int_extract_0 
out/Release/obj/gen/third_party/libvpx/asm_com_offsets.asm

If I restart the build after failure only last two targets are 
mentioned. This means that library is linked successfully. And yes:

# file 
/tmp/ports/usr/ports/www/chromium/work/chromium-courgette-redacted-22.0.1229.79/out/Release/libvpx_obj_int_extract 

/tmp/ports/usr/ports/www/chromium/work/chromium-courgette-redacted-22.0.1229.79/out/Release/libvpx_obj_int_extract: 
ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically 
linked (uses shared libs), not stripped
# nm 
/tmp/ports/usr/ports/www/chromium/work/chromium-courgette-redacted-22.0.1229.79/out/Release/libvpx_obj_int_extract
0000000000601998 d _DYNAMIC
0000000000601b40 d _GLOBAL_OFFSET_TABLE_
                  w _Jv_RegisterClasses
...

So the lib is created correctly, but generating asm offsets somehow 
fails resulting in a zero-length file.

-- 
Sphinx of black quartz, judge my vow.