RE: [iPAQ] Wish List

Jamey Hicks writes:
>
> Cross-compiling is often a headache.
>

Ain't that the truth. Then again, native compilation, (the ideal),
hasn't been painless for me so far. Here's where I'm at:

        1) I'm using a CF ethernet card and chroot to an NFS debian
           install as per the Debian/arm howto. Compilation works
           quite well in this environment until I run out of memory.

        2) Since I keep running out of memory during big compiles I've
           tried to add some swap space. The swapon man pages say,
           "Swap over NFS may not work" and I'm beginning to agree
           there. If I do the mkswap from the iPAQ I always get
           "invalid swap file" from swapon. If I run mkswap from my
           NFS server, then the swapon succeeds, but I get periodic
           messages saying something like "rw_swap: invalid swap
           file", (can't remember the exact message) and processes
           start dying. Any hints from the skiffcluster maintainers
           about how I can get this to work?

        3) Since NFS over swap isn't too happy, I'm now installing a
           Debian image on a microdrive where I also made a swap
           partition. My microdrive is only 340MB so it takes a little
           more care to make sure everything fits. Also, I will no
           longer have access to the network during compilation so
           it's more painful to move files back and forth. :( Yes, the
           USB networking code will help out here... I can't wait! :).

Any suggestions on how to get more robust native compilation?

-Carl

PS. I tried shutting down most processes to free up memory. It seems
like the machine still panics if I keep X off for too long, (it may
have been something I did as well). Has the 10-minute inactivity
console-blanking been disabled as per the earlier suggestion to the
list?
Received on Wed Oct 11 09:23:57 2000