On Sunday 11 April 2010 19:14:13 Charles Manning wrote: > Hello > > I like to do what testing I can on a Ubuntu PC rather than on targets. > > I am currently looking in to a file system issue that does not occur on a > PC with bash, nor does it happen on a busybox built using glibc. > > I'd therefore like to build busybox with uclibc and try that to see if that > reproduces the problem. > > Are there any instructions on how to do that? > > Thanks > > Charles
What target do you want to build it for? (i686? x86_64? powerpc?) Grab the appropriate uClibc cross-compiler-*.tar.bz2 from: http://impactlinx.com/fwl/downloads/binaries Extract it, add its "bin" subdirectory to your $PATH, and then: make defconfig make CROSS_COMPILE=prefix- Where "prefix-" is the prefix for the compiler in question, "i686-" or "x86_64-" and yes the trailing dash is important. You'll probably actually want to build it as: LDFLAGS="--static" make CROSS_COMPILE=i686- So you can run the result on your host. Or you could download a root- filesystem tarball (from the same directory) to chroot into if you want to run the dynamically linked version. If you choose one of the non-x86 targets, the _easy_ thing to do is just grab one of the system-image tarballs, run "./dev-environment.sh", and then wget your source into the /home directory and build in there as normal. (No special flags needed when doing that, even on arm or mips or sparc. This requires you to have installed qemu to emulate the target in question, though. It boots a little virtual machine of the appropraite type, containing native development tools. The advantage of doing it that way is you can run the result in the same environment, to test it out.) That help? Rob -- Latency is more important than throughput. It's that simple. - Linus Torvalds _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
