Ah, that makes sense. I'm building on a well-spec'd VM and then moving the images over to my local machine to run on an emulator from the SDK.
-----Original Message----- From: Stephen Smalley [mailto:s...@tycho.nsa.gov] Sent: Thursday, December 13, 2012 10:07 AM To: Persaud, Ryan K. Cc: seandroid-list@tycho.nsa.gov Subject: Re: Running SEAndroid on the android emulator On 12/13/2012 10:05 AM, Persaud, Ryan K. wrote: > I'm building "seandroid-goldfish-2.6.29 " for ARM. I pasted the wrong > command line in my previous email. The command that did not work for me is: > emulator -show-kernel -kernel kernel/goldfish/arch/arm/boot/zImage > > What I end up seeing on the console is "Uncompressing Linux" repeated many > times followed by "ran out of input data -- System halted." I was able to > successfully load the kernel after adding -qemu -cpu cortex-a8. I meant what version of the userspace - 4.0.4, 4.1.2, 4.2.1, or master? Anyway, I suspect that you are just running some other copy of the emulator (e.g. the one from the android sdk) instead of the one built from the AOSP tree. That would happen if you didn't run lunch in the same shell prior to launching the emulator or otherwise had put the other emulator first in your path. `which emulator` will show you which one. Older emulators defaulted to ARMv5, but modern ones default to ARMv7. -- This message was distributed to subscribers of the seandroid-list mailing list. If you no longer wish to subscribe, send mail to majord...@tycho.nsa.gov with the words "unsubscribe seandroid-list" without quotes as the message.
