How to solve command not found when compiling U-Boot

This article mainly explains "how to solve the problem of command not found when compiling U-Boot". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to solve command not found when compiling U-Boot".

The solution to command not found when compiling U-Boot, the version of U-Boot I use is u-boot-2012.10, and the compilation step is cd u-boot-2012.10make s5p_goni_configsudo make, and then you will see the error message / bin/bash: arm-linux-gcc: command not found dirname: missing operand Try 'dirname-- help' for more information. On the premise that arm-linux-gcc confirms that the installation is correct, the solution is as follows: the command sudo ln-s / opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-gcc / usr/bin/arm-linux-gcc means: establish a symbolic link for the executable file arm-none-linux-gnueabi-gcc under / opt/FriendlyARM/toolschain/4.5.1/bin/, which is under / usr/bin/ / usr/bin/ is the directory referred to by / bin/bash. By the same token, this method can be used to solve any command not found error of this kind at compile time. For example, the corresponding solution for / bin/bash: arm-linux-ld: command not found is sudo ln-s / opt/FriendlyARM/toolschain/4.5.1/bin/arm-none-linux-gnueabi-ld / usr/bin/arm-linux-ld. Thank you for reading. This is the content of "how to solve command not found when compiling U-Boot". After the study of this article I believe that we have a deeper understanding of how to solve this problem when compiling U-Boot, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!