Dear Rob, Thanks for your quick reply! Oooops underlooked the manifest file, sorry: will check versions in details. Aboriginal binary build I used was indeed 1.2.0, however busybox I compiled was 1.20.2 nor 1.20.0 Yes I built static.
The commercial HW target I run it onto (chinese IP cam) is on Linux 2.6.36 (GCC 3.4.2), uClibc 0.9.28...so yes I'm extremely lucky pre-built busybox-mipsel binary runs fine on it! That's why I'm eager to find-out the "magic" aboriginal config that makes it possible! There's no debugger on this target, so I can't trace anything on target I'm afraid. I'm really thinking the issue may be due to the use of aboriginal 1.2.0 mipsel prebuilt binary, which might not match the actual binary busybox build system used to generate busybox-mipsel. Isn't it? I'm going to try to compile aboriginal as described within manifest and check if it builds the same busybox-mipsel... Would it be possible to share the .config file for the actual aboriginal binary busybox build-system used to generate latest busybox-mipsel binary? Thanks again! ----- Mail original ----- De : Rob Landley <[email protected]> À : piquemal michel <[email protected]> Cc : "[email protected]" <[email protected]> Envoyé le : Jeudi 11 avril 2013 21h14 Objet : Re: Prebuild binaries: more detailed setup info/parameters (busybox/aboriginal) ? On 04/11/2013 07:22:16 AM, piquemal michel wrote: > Hi, > I'm trying to build a "small" static busybox for my embedded system (mipsel). > As a starting point, I used pre-built mispsel binaries, from > http://www.busybox.net/downloads/binaries/latest/ > which worked straight out-of-the-box: great! Yay! > Now I wanted to build my own. > README file says it's built with Aboriginal (with no more detail on images > version, use pre-built?, compiler flags?, etc) The MANIFEST file has all the version info. (Note that aboriginal commit 1535 is release 1.2.0, I should fix that so it prioritizes release numbers over commit numbers so you don't have to grovel around in http://landley.net/hg/aboriginal/tags to track that down.) > So I picked-up pre-built Aboriginal system-image-mipsel, and built an > defconfig > busybox for test. > While my resulting defconfig busybox works on that image, it segfaults on my > target. > (tested with several aboriginal images, etc.) Statically linked? > I assume there's magic options/flags used to build those busybox > prebuilt-images on > Aboriginal, or subtle things on the way you build your aboriginal images: > busybox > make defconfig does not seem to cover it all. 1) Try static linking. 2) Run strace against it (http://landley.net/aboriginal/bin has strace binaries for mips). 3) Try an older system-image out of http://landley.net/aboriginal/downloads/old/binaries #3 is because it's possible that the kernel in the image is newer than the one on your target, and although stuff built on older kernels runs on newer ones, stuff built on newer kernels won't always run on older ones. (Linux provides backwards but not forwards compatability. I try to do a new release each kernel, most recent is 3.8 I think.) Rob _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
