Compile error while building chrome for Caroline using simple chrome flow |
||
Issue description
When compiling chrome for Caroline using simple chrome flow, it failed with error:
../../ui/events/ozone/evdev/libgestures_glue/gesture_interpreter_libevdev_cros.cc:215:33: error: no member named 'msc_bitmask' in 'EvdevInfo_'
if (EvdevBitIsSet(evdev->info.msc_bitmask, MSC_TIMESTAMP)) {
~~~~~~~~~~~ ^
../../ui/events/ozone/evdev/libgestures_glue/gesture_interpreter_libevdev_cros.cc:216:50: error: use of undeclared identifier 'Event_Get_Timestamp'
hwstate.msc_timestamp = static_cast<stime_t>(Event_Get_Timestamp(evdev)) /
^
../../ui/events/ozone/evdev/libgestures_glue/gesture_interpreter_libevdev_cros.cc:216:13: error: no member named 'msc_timestamp' in 'HardwareState'; did you mean 'timestamp'?
hwstate.msc_timestamp = static_cast<stime_t>(Event_Get_Timestamp(evdev)) /
^~~~~~~~~~~~~
timestamp
../../../.cros_cache/chrome-sdk/tarballs/caroline+10448.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/include/gestures/gestures.h:169:11: note: 'timestamp' declared here
stime_t timestamp; // 64-bit Wall clock time in microseconds (10^-6 s)
^
../../ui/events/ozone/evdev/libgestures_glue/gesture_interpreter_libevdev_cros.cc:219:13: error: no member named 'msc_timestamp' in 'HardwareState'; did you mean 'timestamp'?
hwstate.msc_timestamp = 0.0;
^~~~~~~~~~~~~
timestamp
../../../.cros_cache/chrome-sdk/tarballs/caroline+10448.0.0+sysroot_chromeos-base_chromeos-chrome.tar.xz/usr/include/gestures/gestures.h:169:11: note: 'timestamp' declared here
stime_t timestamp; // 64-bit Wall clock time in microseconds (10^-6 s)
^
Suspicious CL: https://chromium-review.googlesource.com/c/chromium/src/+/817979
Verified locally that reverting it fixed the compile.
It hasn't reflected on the PFQ yet. I think it will fail the chrome informational builds very soon. I'll revert CL first.
,
Mar 9 2018
Sorry!!! I just did a clobber build (i.e. exit chrome cros_sdk and re-enter it, and delete all the build files in out_caroline/ and rebuild it) and this error went away.
,
Mar 27 2018
Close it. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Mar 9 2018