Build 6.0.1 AOSP master error: unknown target CPU 'pentium2'

601 views
Skip to first unread message

A Qu

unread,
Feb 10, 2016, 10:16:38 AM2/10/16
to Android Building
Hi,
I have downloaded the latest AOSP mater branch (platform 6.0.1). When I try to build, I got this error:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=6.0.1
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.2.0-16-generic-x86_64-with-Ubuntu-15.10-wily
HOST_CROSS_OS=
HOST_CROSS_ARCH=
HOST_CROSS_2ND_ARCH=
HOST_BUILD_TYPE=release
BUILD_ID=MASTER
OUT_DIR=out
============================================
prebuilts/clang/host/linux-x86/clang-2577113/bin/clang++   -fno-exceptions -Wno-multichar -m64 -Wa,--noexecstack -fPIC -no-canonical-prefixes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector -D__STDC_FORMAT_MACROS -D__STDC_CONSTANT_MACROS -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -O2 -g -fno-strict-aliasing -DNDEBUG -UDEBUG  -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument   --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 -fstack-protector-strong    --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -target x86_64-linux-gnu   -Wsign-promo  -Wno-inconsistent-missing-override   --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8 -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/x86_64-linux -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/backward -target x86_64-linux-gnu -c -std=c++11 -g -W -Wall -MMD -MP -O -DNOLOG -march=native -o out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o build/kati/command.cc
error: unknown target CPU 'pentium2'
build/kati/Makefile.ckati:90: recipe for target 'out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o' failed
make: *** [out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/command.o] Error 1
#### make failed to build some targets  ####

The build host OS is Ubuntu 15.10 running on a virtual machine. Any help will be appreciated.

Colin Cross

unread,
Feb 10, 2016, 12:39:53 PM2/10/16
to android-...@googlegroups.com
Try removing the KATI_CFLAGS += -march=native from build/kati/Makefile.ckati
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-buildi...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Hylon

unread,
May 24, 2016, 10:16:44 AM5/24/16
to Android Building
Hi Colin,

Why Google did NOT remove this flag(-march=native) from the official codes?
It seems it will break the build in some scenarios.

e.g. I build the codes on machine A first, and rebuild it on machine B(using some Load Sharing Facility) later after changing some sources, in this scenario, it will cause the build break...

If I clean the built executable kati & rebuild again, it will be successful.

Why Google did NOT consider to clean the built executable kati automatically once such scenarios detected?

Looking forward your reply.  :)

Thanks so much!
Reply all
Reply to author
Forward
0 new messages