Cross-Compiling kernel can't find gcc
I am cross compiling the Raspbian kernel since it will take about 12 hours for the Pi to do (Raspberry Pi 1).
I have the build tools for ARM and the kernel in two separate folders in /home/gray/Desktop/tmp/
I am following this guide: http://elinux.org/Raspberry_Pi_Kernel_Compilation
My issue is that when I go to compile, it can't find arm-linux-gnueabihf-gcc-4.8.3 which is clearly in the folder I linked when I did export CCPREFIX. Here is what I did:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ export CCPREFIX=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-
And it returns when I try to build:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ make ARCH=arm CROSS_COMPILE=${CCPREFIX}
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
Kbuild:43: recipe for target 'kernel/bounds.s' failed
make[1]: *** [kernel/bounds.s] Error 127
Makefile:990: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
Even though the file is clearly in there:
Thanks.
raspberry-pi make gcc raspbian arm
asked Dec 2 '15 at 1:17
GrayGray
62
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am cross compiling the Raspbian kernel since it will take about 12 hours for the Pi to do (Raspberry Pi 1).
I have the build tools for ARM and the kernel in two separate folders in /home/gray/Desktop/tmp/
I am following this guide: http://elinux.org/Raspberry_Pi_Kernel_Compilation
My issue is that when I go to compile, it can't find arm-linux-gnueabihf-gcc-4.8.3 which is clearly in the folder I linked when I did export CCPREFIX. Here is what I did:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ export CCPREFIX=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-
And it returns when I try to build:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ make ARCH=arm CROSS_COMPILE=${CCPREFIX}
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
Kbuild:43: recipe for target 'kernel/bounds.s' failed
make[1]: *** [kernel/bounds.s] Error 127
Makefile:990: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
Even though the file is clearly in there:
Thanks.
raspberry-pi make gcc raspbian arm
asked Dec 2 '15 at 1:17
GrayGray
62
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Try adding/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/binto PATH:export PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin:$PATH
– user140866
Dec 2 '15 at 4:09
Same result. :(
– Gray
Dec 2 '15 at 4:36
This is strange. Either there is a typo somewhere in this long path, or you'd hit a bug. For me alien kernel compilation always worked asmake ARCH=arch CROSS_COMPILE=/path/to/toolchain/bin/toolchain-triplet-. Double check everything, and if still no go, trystrace -f -eexecve -v -s150 -o log make ...and then post result (filelog) on pastebin.com.
– user140866
Dec 2 '15 at 7:03
Is the toolchain complete? You seem not to be able to compile an asm file, not a C file.
– Rui F Ribeiro
Dec 2 '15 at 7:20
I had to truncate it a bit @siblynx pastebin.com/ZdGfP3Qg That is the last bit of the log.
– Gray
Dec 2 '15 at 8:53
add a comment |
I am cross compiling the Raspbian kernel since it will take about 12 hours for the Pi to do (Raspberry Pi 1).
I have the build tools for ARM and the kernel in two separate folders in /home/gray/Desktop/tmp/
I am following this guide: http://elinux.org/Raspberry_Pi_Kernel_Compilation
My issue is that when I go to compile, it can't find arm-linux-gnueabihf-gcc-4.8.3 which is clearly in the folder I linked when I did export CCPREFIX. Here is what I did:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ export CCPREFIX=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-
And it returns when I try to build:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ make ARCH=arm CROSS_COMPILE=${CCPREFIX}
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
Kbuild:43: recipe for target 'kernel/bounds.s' failed
make[1]: *** [kernel/bounds.s] Error 127
Makefile:990: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
Even though the file is clearly in there:
Thanks.
raspberry-pi make gcc raspbian arm
asked Dec 2 '15 at 1:17
GrayGray
62
I am cross compiling the Raspbian kernel since it will take about 12 hours for the Pi to do (Raspberry Pi 1).
I have the build tools for ARM and the kernel in two separate folders in /home/gray/Desktop/tmp/
I am following this guide: http://elinux.org/Raspberry_Pi_Kernel_Compilation
My issue is that when I go to compile, it can't find arm-linux-gnueabihf-gcc-4.8.3 which is clearly in the folder I linked when I did export CCPREFIX. Here is what I did:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ export CCPREFIX=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-
And it returns when I try to build:
gray@Rava-Xubuntu:~/Desktop/tmp/linux$ make ARCH=arm CROSS_COMPILE=${CCPREFIX}
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: 1: /home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: arm-linux-gnueabihf-gcc-4.8.3: not found
Kbuild:43: recipe for target 'kernel/bounds.s' failed
make[1]: *** [kernel/bounds.s] Error 127
Makefile:990: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2
Even though the file is clearly in there:
Thanks.
raspberry-pi make gcc raspbian arm
raspberry-pi make gcc raspbian arm
asked Dec 2 '15 at 1:17
GrayGray
62
asked Dec 2 '15 at 1:17
GrayGray
62
asked Dec 2 '15 at 1:17
GrayGray
62
asked Dec 2 '15 at 1:17
GrayGray
62
asked Dec 2 '15 at 1:17
GrayGray
62
62
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Try adding/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/binto PATH:export PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin:$PATH
– user140866
Dec 2 '15 at 4:09
Same result. :(
– Gray
Dec 2 '15 at 4:36
This is strange. Either there is a typo somewhere in this long path, or you'd hit a bug. For me alien kernel compilation always worked asmake ARCH=arch CROSS_COMPILE=/path/to/toolchain/bin/toolchain-triplet-. Double check everything, and if still no go, trystrace -f -eexecve -v -s150 -o log make ...and then post result (filelog) on pastebin.com.
– user140866
Dec 2 '15 at 7:03
Is the toolchain complete? You seem not to be able to compile an asm file, not a C file.
– Rui F Ribeiro
Dec 2 '15 at 7:20
I had to truncate it a bit @siblynx pastebin.com/ZdGfP3Qg That is the last bit of the log.
– Gray
Dec 2 '15 at 8:53
add a comment |
Try adding/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/binto PATH:export PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin:$PATH
– user140866
Dec 2 '15 at 4:09
Same result. :(
– Gray
Dec 2 '15 at 4:36
This is strange. Either there is a typo somewhere in this long path, or you'd hit a bug. For me alien kernel compilation always worked asmake ARCH=arch CROSS_COMPILE=/path/to/toolchain/bin/toolchain-triplet-. Double check everything, and if still no go, trystrace -f -eexecve -v -s150 -o log make ...and then post result (filelog) on pastebin.com.
– user140866
Dec 2 '15 at 7:03
Is the toolchain complete? You seem not to be able to compile an asm file, not a C file.
– Rui F Ribeiro
Dec 2 '15 at 7:20
I had to truncate it a bit @siblynx pastebin.com/ZdGfP3Qg That is the last bit of the log.
– Gray
Dec 2 '15 at 8:53
Try adding
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin to PATH: export PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin:$PATH– user140866
Dec 2 '15 at 4:09
Try adding
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin to PATH: export PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin:$PATH– user140866
Dec 2 '15 at 4:09
Same result. :(
– Gray
Dec 2 '15 at 4:36
Same result. :(
– Gray
Dec 2 '15 at 4:36
This is strange. Either there is a typo somewhere in this long path, or you'd hit a bug. For me alien kernel compilation always worked as
make ARCH=arch CROSS_COMPILE=/path/to/toolchain/bin/toolchain-triplet-. Double check everything, and if still no go, try strace -f -eexecve -v -s150 -o log make ... and then post result (file log) on pastebin.com.– user140866
Dec 2 '15 at 7:03
This is strange. Either there is a typo somewhere in this long path, or you'd hit a bug. For me alien kernel compilation always worked as
make ARCH=arch CROSS_COMPILE=/path/to/toolchain/bin/toolchain-triplet-. Double check everything, and if still no go, try strace -f -eexecve -v -s150 -o log make ... and then post result (file log) on pastebin.com.– user140866
Dec 2 '15 at 7:03
Is the toolchain complete? You seem not to be able to compile an asm file, not a C file.
– Rui F Ribeiro
Dec 2 '15 at 7:20
Is the toolchain complete? You seem not to be able to compile an asm file, not a C file.
– Rui F Ribeiro
Dec 2 '15 at 7:20
I had to truncate it a bit @siblynx pastebin.com/ZdGfP3Qg That is the last bit of the log.
– Gray
Dec 2 '15 at 8:53
I had to truncate it a bit @siblynx pastebin.com/ZdGfP3Qg That is the last bit of the log.
– Gray
Dec 2 '15 at 8:53
add a comment |
2 Answers
2
active
oldest
votes
I did not able to find where arm-linux-gnueabihf-gcc-4.8.3 is failing from your provided http://pastebin.com/ZdGfP3Qg, but your PATH environment variable contains weird characters:
PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-ras342200214342200213pbian/bin:/home/gray/bin:/usr/local/sbin:/usr/local/bin:/usr/sbi" ...
Those 342200214342200213 in raspbian part should not be there.
Recheck your scripts and set PATH appropriately.
Your CROSS_COMPILE however appears to be intact. Most probably gcc tries to run things from PATH or you have a broken toolchain/dangling symlink somewhere.
Use this strace to debug deeply:
strace -f -v -s150 -o log -eexecve,stat,stat64 (make command) and then do fgrep ENOENT log. Then filter out nonexistent items from your PATH and try to locate and fix remaining items to be on place.
Thanks for the help. I was able to dig through the log and see it was looking for files in a lot of different places. I posted my solution.
– Gray
Dec 2 '15 at 18:09
Nice. So next time using distro provided items is more helpful than messing with own ones. Except the cases when you need your own setup. But in that cases you're already know what to do :-)
– user140866
Dec 2 '15 at 18:21
add a comment |
So I figured it out.
I just grabbed the crossbuild version of gcc (I think that is what it is)
sudo apt-get install crossbuild-essential-armhf
And then my new path is:
export CCPREFIX=/usr/bin/arm-linux-gnueabihf-
And the build works perfectly!
answered Dec 2 '15 at 18:08
GrayGray
62
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f246742%2fcross-compiling-kernel-cant-find-gcc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I did not able to find where arm-linux-gnueabihf-gcc-4.8.3 is failing from your provided http://pastebin.com/ZdGfP3Qg, but your PATH environment variable contains weird characters:
PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-ras342200214342200213pbian/bin:/home/gray/bin:/usr/local/sbin:/usr/local/bin:/usr/sbi" ...
Those 342200214342200213 in raspbian part should not be there.
Recheck your scripts and set PATH appropriately.
Your CROSS_COMPILE however appears to be intact. Most probably gcc tries to run things from PATH or you have a broken toolchain/dangling symlink somewhere.
Use this strace to debug deeply:
strace -f -v -s150 -o log -eexecve,stat,stat64 (make command) and then do fgrep ENOENT log. Then filter out nonexistent items from your PATH and try to locate and fix remaining items to be on place.
Thanks for the help. I was able to dig through the log and see it was looking for files in a lot of different places. I posted my solution.
– Gray
Dec 2 '15 at 18:09
Nice. So next time using distro provided items is more helpful than messing with own ones. Except the cases when you need your own setup. But in that cases you're already know what to do :-)
– user140866
Dec 2 '15 at 18:21
add a comment |
I did not able to find where arm-linux-gnueabihf-gcc-4.8.3 is failing from your provided http://pastebin.com/ZdGfP3Qg, but your PATH environment variable contains weird characters:
PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-ras342200214342200213pbian/bin:/home/gray/bin:/usr/local/sbin:/usr/local/bin:/usr/sbi" ...
Those 342200214342200213 in raspbian part should not be there.
Recheck your scripts and set PATH appropriately.
Your CROSS_COMPILE however appears to be intact. Most probably gcc tries to run things from PATH or you have a broken toolchain/dangling symlink somewhere.
Use this strace to debug deeply:
strace -f -v -s150 -o log -eexecve,stat,stat64 (make command) and then do fgrep ENOENT log. Then filter out nonexistent items from your PATH and try to locate and fix remaining items to be on place.
Thanks for the help. I was able to dig through the log and see it was looking for files in a lot of different places. I posted my solution.
– Gray
Dec 2 '15 at 18:09
Nice. So next time using distro provided items is more helpful than messing with own ones. Except the cases when you need your own setup. But in that cases you're already know what to do :-)
– user140866
Dec 2 '15 at 18:21
add a comment |
I did not able to find where arm-linux-gnueabihf-gcc-4.8.3 is failing from your provided http://pastebin.com/ZdGfP3Qg, but your PATH environment variable contains weird characters:
PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-ras342200214342200213pbian/bin:/home/gray/bin:/usr/local/sbin:/usr/local/bin:/usr/sbi" ...
Those 342200214342200213 in raspbian part should not be there.
Recheck your scripts and set PATH appropriately.
Your CROSS_COMPILE however appears to be intact. Most probably gcc tries to run things from PATH or you have a broken toolchain/dangling symlink somewhere.
Use this strace to debug deeply:
strace -f -v -s150 -o log -eexecve,stat,stat64 (make command) and then do fgrep ENOENT log. Then filter out nonexistent items from your PATH and try to locate and fix remaining items to be on place.
I did not able to find where arm-linux-gnueabihf-gcc-4.8.3 is failing from your provided http://pastebin.com/ZdGfP3Qg, but your PATH environment variable contains weird characters:
PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-ras342200214342200213pbian/bin:/home/gray/bin:/usr/local/sbin:/usr/local/bin:/usr/sbi" ...
Those 342200214342200213 in raspbian part should not be there.
Recheck your scripts and set PATH appropriately.
Your CROSS_COMPILE however appears to be intact. Most probably gcc tries to run things from PATH or you have a broken toolchain/dangling symlink somewhere.
Use this strace to debug deeply:
strace -f -v -s150 -o log -eexecve,stat,stat64 (make command) and then do fgrep ENOENT log. Then filter out nonexistent items from your PATH and try to locate and fix remaining items to be on place.
answered Dec 2 '15 at 9:11
user140866
Thanks for the help. I was able to dig through the log and see it was looking for files in a lot of different places. I posted my solution.
– Gray
Dec 2 '15 at 18:09
Nice. So next time using distro provided items is more helpful than messing with own ones. Except the cases when you need your own setup. But in that cases you're already know what to do :-)
– user140866
Dec 2 '15 at 18:21
add a comment |
Thanks for the help. I was able to dig through the log and see it was looking for files in a lot of different places. I posted my solution.
– Gray
Dec 2 '15 at 18:09
Nice. So next time using distro provided items is more helpful than messing with own ones. Except the cases when you need your own setup. But in that cases you're already know what to do :-)
– user140866
Dec 2 '15 at 18:21
Thanks for the help. I was able to dig through the log and see it was looking for files in a lot of different places. I posted my solution.
– Gray
Dec 2 '15 at 18:09
Thanks for the help. I was able to dig through the log and see it was looking for files in a lot of different places. I posted my solution.
– Gray
Dec 2 '15 at 18:09
Nice. So next time using distro provided items is more helpful than messing with own ones. Except the cases when you need your own setup. But in that cases you're already know what to do :-)
– user140866
Dec 2 '15 at 18:21
Nice. So next time using distro provided items is more helpful than messing with own ones. Except the cases when you need your own setup. But in that cases you're already know what to do :-)
– user140866
Dec 2 '15 at 18:21
add a comment |
So I figured it out.
I just grabbed the crossbuild version of gcc (I think that is what it is)
sudo apt-get install crossbuild-essential-armhf
And then my new path is:
export CCPREFIX=/usr/bin/arm-linux-gnueabihf-
And the build works perfectly!
answered Dec 2 '15 at 18:08
GrayGray
62
add a comment |
So I figured it out.
I just grabbed the crossbuild version of gcc (I think that is what it is)
sudo apt-get install crossbuild-essential-armhf
And then my new path is:
export CCPREFIX=/usr/bin/arm-linux-gnueabihf-
And the build works perfectly!
answered Dec 2 '15 at 18:08
GrayGray
62
add a comment |
So I figured it out.
I just grabbed the crossbuild version of gcc (I think that is what it is)
sudo apt-get install crossbuild-essential-armhf
And then my new path is:
export CCPREFIX=/usr/bin/arm-linux-gnueabihf-
And the build works perfectly!
answered Dec 2 '15 at 18:08
GrayGray
62
So I figured it out.
I just grabbed the crossbuild version of gcc (I think that is what it is)
sudo apt-get install crossbuild-essential-armhf
And then my new path is:
export CCPREFIX=/usr/bin/arm-linux-gnueabihf-
And the build works perfectly!
answered Dec 2 '15 at 18:08
GrayGray
62
answered Dec 2 '15 at 18:08
GrayGray
62
answered Dec 2 '15 at 18:08
GrayGray
62
answered Dec 2 '15 at 18:08
GrayGray
62
62
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f246742%2fcross-compiling-kernel-cant-find-gcc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try adding
/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/binto PATH:export PATH=/home/gray/Desktop/tmp/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin:$PATH– user140866
Dec 2 '15 at 4:09
Same result. :(
– Gray
Dec 2 '15 at 4:36
This is strange. Either there is a typo somewhere in this long path, or you'd hit a bug. For me alien kernel compilation always worked as
make ARCH=arch CROSS_COMPILE=/path/to/toolchain/bin/toolchain-triplet-. Double check everything, and if still no go, trystrace -f -eexecve -v -s150 -o log make ...and then post result (filelog) on pastebin.com.– user140866
Dec 2 '15 at 7:03
Is the toolchain complete? You seem not to be able to compile an asm file, not a C file.
– Rui F Ribeiro
Dec 2 '15 at 7:20
I had to truncate it a bit @siblynx pastebin.com/ZdGfP3Qg That is the last bit of the log.
– Gray
Dec 2 '15 at 8:53