96boards-hikey / aosp-device-linaro-hikey

This repository is based off https://android.googlesource.com/device/linaro/hikey/
12 stars 16 forks source link

fixed build issue with aosp master branch #13

Open ric96 opened 5 years ago

ric96 commented 5 years ago

fix based on: https://android-git.linaro.org/device/linaro/dragonboard410c.git/commit/?h=dragonboard&id=dbe30cae1ef227860089e1840aeb1cd140c0003a

hostapd: Add HIDL interface and remove deprecated sepolicies Add hostapd HIDL interface and remove deprecated hostapd sepolicies since AOSP no longer have a predefined hostapd domain and we run into "ERROR 'unknown type hostapd'" build error instead.

Signed-off-by: Sahaj Sarup sahaj.sarup@linaro.org

ric96 commented 5 years ago

Requesting review @docularxu

daniel-thompson commented 5 years ago

Forgive me being didactic but do the resulting binaries boot to GUI?

ric96 commented 5 years ago

@daniel-thompson I just checked, it's not booting to GUI for me. So this just fixes the build. Adding boot log for reference https://pastebin.com/1cxL415C

pundiramit commented 5 years ago

On Wed, 26 Dec 2018 at 11:06, Sahaj Sarup notifications@github.com wrote:

@daniel-thompson I just checked, it's not booting to GUI for me. So this just fixes the build. Adding boot log for reference https://pastebin.com/1cxL415C

init: [libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt init: Failed to read fstab from device tree init: [libfs_mgr]fs_mgr_read_fstab_default(): failed to find device default fstab init: [libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt init: First stage mount skipped (missing/incompatible/empty fstab in device tree)

This ^^ is a fatal error. Fstab DT entries are no longer optional.

Ref: https://android-git.linaro.org/device/linaro/dragonboard410c.git/commit/?h=dragonboard&id=9b534d9c5e24656c680f029f144e4e4a08f2899f https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/commit/?h=release/android/qcomlt-4.14&id=7f14045de13cd7e73030e11368fd193a4efc5db9

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.