![]() You can change to a different branch (instructions from 2): git git fetch git:///raspberrypi/linux.git git checkout rpi-4.18.y This is usually the most recent stable branch. You generally don’t need the commit history, so to speed up the process, you can alternatively use the -depth argument to only clone the most recent version of all the files: git clone -depth=1 Then, clone the kernel source code from Github: mkdir cd git clone Build will fail with a very obscure error otherwise ( 7).Ĭreate a folder for storing the Linux source code. Important! If you are using a virtual machine, clone the source code into a folder directly in the vm, not a shared directory. ![]() In order to install it: git clone echo PATH=$PATH:~/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-圆4/bin > source ~/.bashrc 2. My MacBook uses the x86 processor architecture (as most modern computers do), and luckily, the Raspberry Pi Foundation has published an x86 cross-compiler toolchain for the Raspberry Pi. In order to compile source code into machine code that is not native to the build machine, a cross-compiler has to be used. However, the steps should be the same independent of whether you’re using a virtual machine or not, running a different version of Linux, etc. I’m using Ubuntu 16.04 running inside a Parallels virtual machine. Although I found some tutorials describing the process, I had to adapt and combine them in a few places, so I decided to publish the steps that eventually worked for me in a blog post. Instead of compiling the kernel on the Pi itself, I wanted to speed up the process by running it inside a Ubuntu virtual machine on my MacBook Pro. I recently had to compile a custom kernel for my Raspberry Pi.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |