root@ubuntu:~/Documents/work_dir# lunch
You're building on Linux
Lunch menu... pick a combo: 1. aosp_arm-eng 2. aosp_arm64-eng 3. aosp_mips-eng 4. aosp_mips64-eng 5. aosp_x86-eng 6. aosp_x86_64-eng 7. full_fugu-userdebug 8. aosp_fugu-userdebug 9. car_emu_arm64-userdebug 10. car_emu_arm-userdebug 11. car_emu_x86_64-userdebug 12. car_emu_x86-userdebug 13. mini_emulator_arm64-userdebug 14. m_e_arm-userdebug 15. m_e_mips64-eng 16. m_e_mips-userdebug 17. mini_emulator_x86_64-userdebug 18. mini_emulator_x86-userdebug 19. aosp_dragon-userdebug 20. aosp_dragon-eng 21. aosp_marlin-userdebug 22. aosp_marlin_svelte-userdebug 23. aosp_sailfish-userdebug 24. aosp_angler-userdebug 25. aosp_bullhead-userdebug 26. aosp_bullhead_svelte-userdebug 27. hikey-userdebug
Which would you like? [aosp_arm-eng] 25
============================================PLATFORM_VERSION_CODENAME=RELPLATFORM_VERSION=8.0.0TARGET_PRODUCT=aosp_bullheadTARGET_BUILD_VARIANT=userdebugTARGET_BUILD_TYPE=releaseTARGET_PLATFORM_VERSION=OPR1TARGET_BUILD_APPS=TARGET_ARCH=arm64TARGET_ARCH_VARIANT=armv8-aTARGET_CPU_VARIANT=cortex-a53TARGET_2ND_ARCH=armTARGET_2ND_ARCH_VARIANT=armv7-a-neonTARGET_2ND_CPU_VARIANT=cortex-a53.a57HOST_ARCH=x86_64HOST_2ND_ARCH=x86HOST_OS=linuxHOST_OS_EXTRA=Linux-3.13.0-24-generic-x86_64-with-Ubuntu-14.04-trustyHOST_CROSS_OS=windowsHOST_CROSS_ARCH=x86HOST_CROSS_2ND_ARCH=x86_64HOST_BUILD_TYPE=releaseBUILD_ID=OPR6.170623.010OUT_DIR=outAUX_OS_VARIANT_LIST=============================================root@ubuntu:~/Documents/work_dir# emulator -partition-size 1024emulator: WARNING: userdata partition is resized from 142 M to 1024 M
ERROR: resizing partition e2fsck failed with exit code 8emulator: WARNING: encryption is offqemu-system-aarch64: Trying to execute code outside RAM or ROM at 0x0000000000000400This usually means one of the following happened:
(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end(3) Your guest kernel has a bug and crashed by jumping off into nowhere
This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.
Execution cannot continue; stopping here.
QObject::~QObject: Timers cannot be stopped from another threadroot@ubuntu:~/Documents/work_dir#
--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/b9341e65-64b5-4804-996e-c2153f31f755%40googlegroups.com.