Hi Zuber On Tue, Oct 28, 2008 at 6:06 AM, <[email protected]> wrote: > to help during compilation. But the big problem is the configure script, > it takes ages to complete.
One reason you might have noticed that configure takes a really long time to execute on an embedded computer, is that you're running configure on the '/' filesystem. Configure is constantly creating and deleting files, basically 1 for each test it performs, which can be really slow on many block devices (particularly flash). These days, when I emerge, either on my desktop or on an ARM board, I always try to do it in /tmp, which I've mounted as tmpfs (i.e. ram). However, for big builds, you run the risk of over-allocating ram, which can crash linux. I wouldn't try this for perl, in any case, unless the embedded device has a few hundred MB of ram, but for smaller packages that need to be natively compiled (i.e. bash) it works very well. Cheers Chris PS: lf you still want to try compiling in RAM, mount -t tmpfs none /tmp export PORTAGE_TMPDIR=/tmp I actually use a similar environment full-time on my 8G eee pc
