ERROR: build kernel Failed
Discussion in "ARM Development" started by Samimash May 16, 2017.
Tue May 16 2017, 06:56 pm
hello friends
i recently got a nanopi m1,i begin with the official documentation :"http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M1#Make_Your_Own_Debian"
i downloaded the lichee source code and this toolchain:gcc-linaro-arm.tar.xz as the document said
but when i try to compile the source code,i got this error:
is it a compiler problem?
i am running Ubuntu 17.04 and i am a beginner in both arm processor and Linux environment but i have a background in electronics
thank you
![]()
i recently got a nanopi m1,i begin with the official documentation :"http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M1#Make_Your_Own_Debian"
i downloaded the lichee source code and this toolchain:gcc-linaro-arm.tar.xz as the document said
but when i try to compile the source code,i got this error:
arm-linux-gnueabi-gcc: error trying to exec 'cc1': execvp: No such file or directory ERROR: build kernel Failed
is it a compiler problem?
i am running Ubuntu 17.04 and i am a beginner in both arm processor and Linux environment but i have a background in electronics
thank you

[ Edited Tue May 16 2017, 06:57 pm ]
Tue May 16 2017, 10:35 pm
I'm sure this is a compiler / Linux problem.
In Linux, what you type is critical, every letter and space counts.
Directory paths are critical.
Did you set up the directories exactly as directed, same names, including
upper case and lower case letters ?
Have you switched to the right directory before starting to compile ?
You will probably get better help from a Linux support site.
If you want to keep trying here...
post a screen shot of exactly what you were doing when you got the message.
Clearly the compiler can't find the file "cc1" . Do you know what file that is ,
or is "cc1" a spelling mistake ?
In Linux, what you type is critical, every letter and space counts.
Directory paths are critical.
Did you set up the directories exactly as directed, same names, including
upper case and lower case letters ?
Have you switched to the right directory before starting to compile ?
You will probably get better help from a Linux support site.
If you want to keep trying here...
post a screen shot of exactly what you were doing when you got the message.
Clearly the compiler can't find the file "cc1" . Do you know what file that is ,
or is "cc1" a spelling mistake ?
[ Edited Tue May 16 2017, 10:49 pm ]
Samimash like this.
Wed May 17 2017, 10:07 am
thank you for your reply friend
'cc1' is a file actually
whole code :
'cc1' is a file actually
whole code :
./build.sh -p sun8iw7p1 -b nanopi-h3 INFO: ---------------------------------------- INFO: build lichee ... INFO: chip: sun8iw7p1 INFO: platform: linux INFO: business: INFO: kernel: linux-3.4 INFO: board: nanopi-h3 INFO: output: out/sun8iw7p1/linux/nanopi-h3 INFO: ---------------------------------------- INFO: build kernel ... INFO: prepare toolchain ... INFO: skip kernel clean for nanopi-h3 Linux system. Building kernel /home/sami/lichee/linux-3.4/output/lib/modules/3.4.39-h3 CHK include/linux/version.h CHK include/generated/utsrelease.h make[1]: 'include/generated/mach-types.h' is up to date. CC kernel/bounds.s arm-linux-gnueabi-gcc: error trying to exec 'cc1': execvp: No such file or directory /home/sami/lichee/linux-3.4/./Kbuild:35: recipe for target 'kernel/bounds.s' failed make[1]: *** [kernel/bounds.s] Error 1 Makefile:986: recipe for target 'prepare0' failed make: *** [prepare0] Error 2 make: *** Waiting for unfinished jobs.... CC scripts/mod/empty.o arm-linux-gnueabi-gcc: error trying to exec 'cc1': execvp: No such file or directory scripts/Makefile.build:307: recipe for target 'scripts/mod/empty.o' failed make[2]: *** [scripts/mod/empty.o] Error 1 scripts/Makefile.build:443: recipe for target 'scripts/mod' failed make[1]: *** [scripts/mod] Error 2 Makefile:507: recipe for target 'scripts' failed make: *** [scripts] Error 2 ERROR: build kernel Failed INFO: use a fake rootfs.ext4. 1+0 records in 1+0 records out 1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00234644 s, 447 MB/s mke2fs 1.43.4 (31-Jan-2017) Filesystem too small for a journal INFO: ---------------------------------------- INFO: build sun8iw7p1 linux lichee OK INFO: ----------------------------------------
[ Edited Wed May 17 2017, 01:36 pm ]
Fri May 19 2017, 04:58 am
Linux can be a minefield of make files, scripts and path settings.
If you find file 'cc1' on your system you might be able to see why it can't be found.
It might not even be included in the packages you downloaded.
I see that the page
"http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M1#Make_Your_Own_Debian"
offers pre-built images.
Honestly, I'd use one of them, and come back to "Make_Your_Own_Debian" when you
have a week or two to spare.
If you find file 'cc1' on your system you might be able to see why it can't be found.
It might not even be included in the packages you downloaded.
I see that the page
"http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M1#Make_Your_Own_Debian"
offers pre-built images.
Honestly, I'd use one of them, and come back to "Make_Your_Own_Debian" when you
have a week or two to spare.
Fri May 19 2017, 12:31 pm
To me it looks like your development environment is not setup properly.
Did you clone the repo successfully? Any missing file or failed clone can lead to issue.
You can try to reset your repo the the head and try to build again.
Did you install all the dependency packages correctly?
Did you clone the repo successfully? Any missing file or failed clone can lead to issue.
git clone https://github.com/friendlyarm/h3_lichee.git lichee
You can try to reset your repo the the head and try to build again.
# git reset --hard
Did you install all the dependency packages correctly?
sudo apt-get install gawk git gnupg flex bison gperf build-essential \ zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \ libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \ libgl1-mesa-dev g++-multilib mingw32 tofrodos \ python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Powered by e107 Forum System