Because I recently bought a Tiny4412 (Exynos4412) board, it is also a cross-compilation tool chain that Tiny4412 needs to use.
Development environment: ubuntu-12.04
Target board: Tiny4412
1. Copy the arm-linux-gcc-4.5.1-v6-vfp.tgz to the Ubuntu virtual machine/SMB directory via the Samba server
2. Since my working directory is under/xplan, create a new Toolschain directory below/xplan
# Cd/xplan
# MKIDR toolschain
# CD Toolschain
3. Move the arm-linux-gcc-4.5.1-v6-vfp.tgz under the/SMB directory to/xplan/toolschain
# Mv/smb/arm-linux-gcc-4.5.1-v6-vfp.tgz/xplan/toolschain
4. Unzip the arm-linux-gcc-4.5.1-v6-vfp.tgz
# tar XZVF arm-linux-gcc-4.5.1-v6-vfp.tgz
5. After extracting a 4.5.1 directory in the Toolschain directory, we need to use the cross-compiler tool (GCC,LD, etc.) under 4.5.1/bin/, the next step is to add the cross-compilation tool path to the environment change
In volume $path, there are many ways to add path, and it is common practice to add it in/etc/profile and restart it on the Internet. As we add to the/etc/profile file as $path=$ (PATH):/xplan/toolschain/4.5.1/bin,
and then reboot. However, since I often need to use different platforms in the actual work of the Development Board, the different vendors will provide their own toolschain, if not all of them are added to the/etc/profile, it is important to make an error.
So can only be used each time the export, wrote a script, every time you log in to Ubuntu, execute a bit can
#! /bin/bash
Topdir=/xplan
export arch=arm export
cross_compile=arm-linux-
export path= "$PATH: $ Topdir/toolschain/4.5.1/bin "
6. Finally verify that the installation is complete, arm-linux-gcc-v if the display is correct, then the installation is complete.
# arm-linux-gcc-v