Sorry for the stupid question but if I do not build NOMMU busybox correctly can you please give me a hint where I have to make a change ? All the other applets do work and I think that all other applets are using vfork without me making any modification
You did say that the -DBB_NOMMU is not a correct option so its possible (likely) I do make a error on the building but please tell me what I need to do to make it build correct ? so again I use: "make ARCH=arm CROSS_COMPILE=arm-uclinux-elf- EXTRA_CFLAGS="-D__uClinux__ -DSKIP_STRIP=y" LDFLAGS="-Wl,-elf2flt" install" and I was thinking that the uClinux flag was giving the correct option for NOMMU (uClinux is always without MMU) but let me repeat that I have no C skills at all so I have no clue what to change in the way I need to build NOMMU busybox correctly /martinb -----Oorspronkelijk bericht----- Van: Denys Vlasenko [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 8 januari 2008 13:37 Aan: Alex Landau CC: [email protected]; Martinb_ARM_NOMMU_KISSDVD Onderwerp: Re: Fw: Hush cant replace lash for my situation On Tuesday 08 January 2008 06:33, Alex Landau wrote: > > #if BB_MMU > > child->pid = fork(); > > + debug_printf_exec(": vfork returned %d\n", child->pid); > > #else > > child->pid = vfork(); > > + debug_printf_exec(": fork returned %d\n", child->pid); > > #endif > Denys, > It prints vfork(), but actually executes fork() (a typo in your patch below), so I'd say > busybox does not recognize that this is a NOMMU system. > Alex Thanks Alex! Yes, I mistakenly interchanged fork/vfork _in debug messages ONLY_. fork/vfork itself is correct (straignt for 0.9.0 tarball): #if BB_MMU child->pid = fork(); #else child->pid = vfork(); #endif Martin, you definitely do not build NOMMU busybox correctly. In your build, BB_MMU is set to 1. -- vda _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
