Thanks for the hint. Couldn’t find anything in any of the device mk’s with that wording but I did find something similar by following a trail to device/google/gs101/aosp_common.mk
It’s building now but a hell of a lot of warnings (purple). Is that normal?
I’ll let it run and see what happens.
Update: #########################################################################
Build failed after 4+ hours. Difficult to interpret the output running in terminal but I find many types of error logs in ~/android/lineage/out. I focus on the series named “error.log.1” etc. of which the numbered files all seemed to be from a previous build run. The last one named error.log ran to 323 lines, the last line was:
“ERROR: Dex2oat failed to compile a boot image.It is likely that the boot classpath is inconsistent.Rebuild with ART_BOOT_IMAGE_EXTRA_ARGS=”–runtime-arg -verbose:verifier" to see verification errors."
Found something on Stackflow, but not sure about it. Further research into SSE4.2 shows it depends on the pc’s processor as to whether it is present or not.
“Just disable optimization for the sse4.2/popcount in the file ./art/build/Android.bp
:”
host: {
cflags: [
// Bug: 15446488. We don't omit the frame pointer to work around
// clang/libunwind bugs that cause SEGVs in run-test-004-ThreadStress.
"-fno-omit-frame-pointer",
// The build assumes that all our x86/x86_64 hosts (such as buildbots and developer
// desktops) support at least sse4.2/popcount. This firstly implies that the ART
// runtime binary itself may exploit these features. Secondly, this implies that
// the ART runtime passes these feature flags to dex2oat and JIT by calling the
// method InstructionSetFeatures::FromCppDefines(). Since invoking dex2oat directly
// does not pick up these flags, cross-compiling from a x86/x86_64 host to a
// x86/x86_64 target should not be affected.
//"-msse4.2",
//"-mpopcnt",
],
},
Another update: ###################################################################
Got into a mess attempting to follow the above “fix” so reinstated the original Android.bp file. Checked through the error logs in out and ran the build again.
Surprisingly it succeeded in 16 mins!
So now I’ll have to back up my phone before it gets wiped and take it for a spin.