Bug 200487 - www/chromium: Fails to compile. Media Transfer Protocol error: "Only used on Linux and ChromeOS"
Summary: www/chromium: Fails to compile. Media Transfer Protocol error: "Only used on ...
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-chromium (Nobody)
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2015-05-27 20:39 UTC by pete
Modified: 2017-01-17 17:36 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (chromium)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pete 2015-05-27 20:39:36 UTC
I have an reproducible segfault and coredump with version 43.0.2357.65 installed via pkg.  I have attempted to do a local build with debug symbols to extract more data from the segfault and the build fails like so:


In file included from ../../components/storage_monitor/test_media_transfer_protocol_manager_linux.h:8:
../../device/media_transfer_protocol/media_transfer_protocol_manager.h:16:2: error: "Only used on Linux and ChromeOS"
#error "Only used on Linux and ChromeOS"
 ^
../../components/storage_monitor/test_media_transfer_protocol_manager_linux.cc:7:10: fatal error: 'device/media_transfer_protocol/mtp_file_entry.pb.h' file not found
#include "device/media_transfer_protocol/mtp_file_entry.pb.h"
         ^
2 errors generated.
[5116/21560] AR obj/dbus/libdbus_test_support.a
[5116/21560] AR obj/v8/tools/gyp/libv8_base.a
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/chromium
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium




using the MAKE_JOBS_UNSAFE=yes flag results in the following:


> sudo make WITH_DEBUG=yes MAKE_JOBS_UNSAFE=yes
===>  Building for chromium-43.0.2357.65
ninja: Entering directory `out/Debug'
[3/16445] CXX obj/components/storage_monitor/storage_monitor_test_support.test_media_transfer_protocol_manager_linux.o
FAILED: c++ -MMD -MF obj/components/storage_monitor/storage_monitor_test_support.test_media_transfer_protocol_manager_linux.o.d -DV8_DEPRECATION_WARNINGS -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC -DDISABLE_NACL -DCHROMIUM_BUILD -DCR_CLANG_REVISION=233105-1 -DTOOLKIT_VIEWS=1 -DUSE_AURA=1 -DUSE_ASH=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 -DUSE_CLIPBOARD_AURAX11=1 -DENABLE_ONE_CLICK_SIGNIN -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DUSE_PROPRIETARY_CODECS -DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DDONT_EMBED_BUILD_METADATA -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1 -DCLD_VERSION=2 -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_SUPERVISED_USERS=1 -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 -DUSE_LIBPCI=1 -DUSE_GLIB=1 -DUSE_NSS=1 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DWTF_USE_DYNAMIC_ANNOTATIONS=1 -D_DEBUG -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Igen/shim_headers/libevent/target -Igen -I../.. -fstack-protector --param=ssp-buffer-size=4  -pthread -fno-strict-aliasing -Wall -Wno-unused-parameter -Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC -Wno-reserved-user-defined-literal -fcolor-diagnostics -Wheader-hygiene -Wno-char-subscripts -Wno-unneeded-internal-declaration -Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing -Wno-deprecated-register -Wno-inconsistent-missing-override -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -m64 -march=x86-64 -O0 -g -gdwarf-4 -funwind-tables -Wno-undefined-bool-conversion -Wno-tautological-undefined-compare -pipe -isystem/usr/local/include -I/usr/local/include/atk-1.0 -Wno-unknown-warning-option -g -fstack-protector -fno-strict-aliasing -fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -Wsign-compare -std=gnu++11  -c ../../components/storage_monitor/test_media_transfer_protocol_manager_linux.cc -o obj/components/storage_monitor/storage_monitor_test_support.test_media_transfer_protocol_manager_linux.o
In file included from ../../components/storage_monitor/test_media_transfer_protocol_manager_linux.cc:5:
In file included from ../../components/storage_monitor/test_media_transfer_protocol_manager_linux.h:8:
../../device/media_transfer_protocol/media_transfer_protocol_manager.h:16:2: error: "Only used on Linux and ChromeOS"
#error "Only used on Linux and ChromeOS"
 ^
../../components/storage_monitor/test_media_transfer_protocol_manager_linux.cc:7:10: fatal error: 'device/media_transfer_protocol/mtp_file_entry.pb.h' file not found
#include "device/media_transfer_protocol/mtp_file_entry.pb.h"
         ^
2 errors generated.
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/chromium
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium
Comment 1 pete 2015-05-27 21:05:25 UTC
This build error is also reproducible when attempting to compile with out debug flags passed to make.
Comment 2 pete 2015-05-28 23:51:00 UTC
I have isolated this issue to only happening when chromium is build with the "Tests" configuration option enabled.  I am able to successfully build the binary, with debugging enabled, when I disable tests.
Comment 3 pete 2015-05-28 23:59:27 UTC
(In reply to pete from comment #2)
unfortunately while the binary builds it is unusable:

> ldd /usr/ports/www/chromium/work/stage/usr/local/share/chromium/chrome
/usr/ports/www/chromium/work/stage/usr/local/share/chromium/chrome:
/usr/ports/www/chromium/work/stage/usr/local/share/chromium/chrome: signal 6

running make install also results in an unusable binary.  going to attempt to rebuild without debug flags to see if this results in a usable binary, although i suspect it will still segfault shortly after startup which is what I am seeing from the official chromium pkg.
Comment 4 pete 2017-01-17 17:36:01 UTC
This is for an old Chrome version so closing issue to clean up queue.