Comment 6 for bug 1473680

I looked to upload this just now. I followed the request in comment #4 to build oxide with it. The oxide build fails with an unrelated error.

FAILED: /usr/bin/x86_64-linux-gnu-g++ -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -fuse-ld=gold -Wl,--disable-new-dtags -Wl,--stats -m64 -Wl,--detect-odr-violations -Wl,--icf=all -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -o protoc -Wl,--start-group obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/protoc.code_generator.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/protoc.command_line_interface.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/protoc.plugin.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/protoc.plugin.pb.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/protoc.subprocess.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/protoc.zip_writer.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_enum.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_enum_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_extension.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_file.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_generator.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_helpers.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_message.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_message_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_primitive_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_service.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/cpp/protoc.cpp_string_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_enum.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_enum_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_extension.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_file.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_generator.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_helpers.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_message.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_message_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_primitive_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_service.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/java/protoc.java_string_field.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/python/protoc.python_generator.o obj/third_party/chromium/src/third_party/protobuf/src/google/protobuf/compiler/protoc.main.o obj/third_party/chromium/src/third_party/protobuf/libprotobuf_full_do_not_use.a -Wl,--end-group
/usr/bin/ld.gold: --push-state: unknown option
/usr/bin/ld.gold: use the --help option for usage information
collect2: error: ld returned 1 exit status

Maybe we should wait for this to get fixed. It seems to be bug #1496743