Thanks for your answer, Chen. I guess since I'm building on a 64bit system for a 32bit system I should add a cross compile flag like make menuconfig CROSS_COMPILE=i386?
On Mar 10, 1:23 pm, Chen Yang <[email protected]> wrote: > Dani: > If build statically, you don't need to configure with Android. You > just need to configure busybox by: make menuconfig > Hope it helps. > -- > Chen > > On Tue, Mar 10, 2009 at 8:18 PM, squix <[email protected]> wrote: > > > Did you get busybox to run on x86? If yes, how did your build commands > > look like, how your Android.mk? > > > Dani > > > On Feb 4, 7:36 pm, AndyM <[email protected]> wrote: > >> when you buildbusy boxthere is an option to build statically. That > >> may be your best bet to get it running on x86. > > >> On Feb 4, 1:02 pm, Zia <[email protected]> wrote: > > >> > Thanks Chen. > > >> > -Zia > > >> > On Feb 3, 4:52 pm, Chen Yang <[email protected]> wrote: > > >> > > hi Zia: > >> > > It's not in the kernel, it's in thebusybox. You can download the > >> > >BusyBoxsource and config it using make menuconfig. > >> > > -- > >> > > Chen > > >> > > On Wed, Feb 4, 2009 at 8:46 AM, Zia <[email protected]> wrote: > > >> > > > I'm looking to runBusyBoxon Andoird x86 port (on VMware for now). > >> > > > Looking through the group, I noticed this post > >> > > >http://groups.google.com/group/android-porting/browse_thread/thread/6... > > >> > > > However, I dont see the option ofBusyBoxsettings in ($mydroid/ > >> > > > kernel: make menuconfig). It seems I'm missing something in the > >> > > > source > >> > > > tree or in the config files. Any ideas about it? > > >> > > > My aim is to run Dropbear withBusyBoxon Android x86. > > >> > > > Please advice. > > >> > > > Thanks, --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
