[flatfish] Build break by "fatal error: hardware/bt_rc.h: No such file or directory"

RESOLVED FIXED in 2.2 S5 (6feb)

Status

Firefox OS
General
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: dliang, Assigned: shawnjohnjr)

Tracking

unspecified
2.2 S5 (6feb)
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
Created attachment 8558298 [details]
build.log

error log:
system/bluetoothd/src/bt-rc-io.c:20:28: fatal error: hardware/bt_rc.h: No such file or directory
compilation terminated.
target thumb C: dbus-daemon <= external/dbus/bus/config-loader-expat.c
target thumb C: dbus-daemon <= external/dbus/bus/config-parser.c
make: *** [out/target/product/flatfish/obj/EXECUTABLES/bluetoothd_intermediates/bt-rc-io.o] Error 1
make: *** Waiting for unfinished jobs....
(Reporter)

Updated

4 years ago
Summary: [flatfish] Fix build break by "fatal error: hardware/bt_rc.h: No such file or directory" → [flatfish] Build break by "fatal error: hardware/bt_rc.h: No such file or directory"
(Reporter)

Updated

4 years ago
Summary: [flatfish] Build break by "fatal error: hardware/bt_rc.h: No such file or directory" → [flatfish] Build break by "fatal error: hardware/bt_rc.h: No such file or directory"
Thanks for reporting. It looks like build flag is missing.
Assignee: nobody → shuang
Created attachment 8558352 [details] [review]
Bug 1128815 - Fix build break for API version lower than 18
Attachment #8558352 - Flags: review?(tzimmermann)
I've tested on flatfish, this can fix bluetoothd build break.
Comment on attachment 8558352 [details] [review]
Bug 1128815 - Fix build break for API version lower than 18

Thanks Shawn!
Attachment #8558352 - Flags: review?(tzimmermann) → review+
Keywords: checkin-needed
https://github.com/mozilla-b2g/platform_system_bluetoothd/commit/23d746289c21673448b00a31dd469cbf0b23b26e
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S5 (6feb)
You need to log in before you can comment on or make changes to this bug.