I had followed the eLinux wiki instructions: http://elinux.org/RPi_Kernel_Compilation
Here's how I compiled my kernel back in April:
I need to do it again soon, so I'll have to see if I pick up any new tricks this time around.
update: bootc.net documents a different approach but I've not tried it yet: http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/
I thought I might try compiling a kernel on my mac using the instructions on the eLinux wiki webpage you gave me. Under the heading -
From a foreign machine
git clone git://github.com/raspberrypi/firmware.git
scp arm128_start.elf arm192_start.elf arm224_start.elf bootcode.bin loader.bin start.elf <user>@<host>:/boot/
I'm not sure about this part of the last line <user>@<host>:/boot/ . I found out host is a command but not sure if I need to replace user with something else <user>.
Hi, that last line is to copy those files ( arm128_start.elf arm192_start.elf arm224_start.elf bootcode.bin loader.bin start.elf ) to the Pi over the network via scp (secure copy, which is part of the ssh family of utilities). Let's say my Pi is at 192.168.1.10 and my Pi username is 'pi'. The command would be:
scp arm128_start.elf arm192_start.elf arm224_start.elf bootcode.bin loader.bin start.elf firstname.lastname@example.org:/boot/
It should then prompt for password which would be 'raspberry' for user 'pi' on the default Raspbian Wheezy.
I have a Airport Express connected to a cable modem when I issue the command
scp arm128_start.elf arm192_start.elf arm224_start.elf bootcode.bin loader.bin start.elf email@example.com:/boot/
ssh: connect to host 10.0.1.2 port 22: Connection refused
At this point I don't know why the connection was refused. Any hints on where I might start looking?
Ah, I think the ssh server process (sshd) needs to be started on the Pi. You should be able to do this via raspi-config. On Raspbian Wheezy, the command should be:
Cross-compiling on a more powerful machine is of course the sensible thing to do, not only for speed but to avoid an enormous number of rewrite cycles on the SD card.
Just out of curiosity though, has anyone actually timed how long it would take to compile a kernel natively on Pi? I'm also curious about whether the main thing that constrains native compilation speed on Pi is CPU or filestore.