Summary: | www/chromium: chromium-43.0.2357.130 build fails to compile | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Tony Narlock <tony> |
Component: | Individual Port(s) | Assignee: | freebsd-chromium (Nobody) <chromium> |
Status: | Closed Unable to Reproduce | ||
Severity: | Affects Only Me | CC: | rene |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(chromium) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Tony Narlock
2015-06-30 11:21:55 UTC
After looking further, this doesn't seem to be limited to DEBUG. It happens on default builds as well. ===> The following configuration options are available for chromium-43.0.2357.130: CODECS=on: Compile and enable patented codecs like H.264 DEBUG=off: Build with debugging support GCONF=off: GConf configuration backend support KERBEROS=on: Kerberos support PULSEAUDIO=off: PulseAudio sound server support TEST=off: Build and/or run tests ===> Use 'make config' to modify these settings Error: [2678/16857] CXX obj/base/process/base.memory.o ../../base/process/memory.cc:67:48: warning: backslash and newline separated by space #if defined(MEMORY_TOOL_REPLACES_ALLOCATOR) || \ ^ [2748/16857] CXX obj/base/base.sys_info_posix.o ../../base/sys_info_posix.cc:57:5: warning: '{anonymous}::g_lazy_number_of_processors' defined but not used [-Wunused-variable] g_lazy_number_of_processors = LAZY_INSTANCE_INITIALIZER; ^ [3297/16857] CXX obj/components/storage_monitor/storage_monitor.storage_monitor_freebsd.o ../../components/storage_monitor/storage_monitor_freebsd.cc:45:29: warning: 'storage_monitor::StorageMonitor::EjectStatus storage_monitor::{anonymous}::EjectPathOnFileThread(const base::FilePath&, const base::FilePath&)' defined but not used [-Wunused-function] StorageMonitor::EjectStatus EjectPathOnFileThread( ^ [5189/16857] ACTION v8_snapshot: run_mksnapshot_01abb6e5ba7d6feae165fcbae91bf365 FAILED: cd ../../v8/tools/gyp; ../../../out/Release/mksnapshot --log-snapshot-positions --logfile ../../../out/Release/obj/v8/tools/gyp/v8_snapshot.gen/snapshot.log --random-seed 314159265 ../../../out/Release/obj/v8/tools/gyp/v8_snapshot.gen/snapshot.cc "" [5189/16857] CXX obj/extensions/common/api/gen/extensions/common/api/extensions_api.usb.o 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 Your log does not show the actual compilation error, what happens if you run the command manually, i.e.: cd ../../v8/tools/gyp; ../../../out/Debug/mksnapshot --log-snapshot-positions --logfile ../../../out/Debug/obj/v8/tools/gyp/v8_snapshot.gen/snapshot.log --random-seed 314159265 ../../../out/Debug/obj/v8/tools/gyp/v8_snapshot.gen/snapshot.cc "" Also, can you update devel/py-ply to r390980 ? I just updated Chromium to version 43.0.2357.132, does the problem still exist? It builds fine in a clean Poudriere jail. Thank you Rene, I have not been able to replicate this bug. I have two correct builds, and unfortunately since I wasn't paying attention, I didn't nail down *specifically* what changed between this ticket and now: - a few days ago at chromium-43.0.2357.130. The difference is in between my ticket's creation and then, I altered my /etc/make.conf. I believe it may have been the CC/CPP= flags I had set. - with 43.0.2357.132: I also get a clean build I am closing this ticket. Should the same big present itself I will follow up with the information requested. |