Jan 23, 2016 Code: Select all root@cockpit # uname -a Linux cockpit.00steven.net 3.10.0-327.4.4.el7.x8664 #1 SMP Tue Jan 5 16:07:00 UTC 2016 x8664 x8664 x8664 GNU/Linux.
I downloaded toolchain from parrot Github, installed, now I am trying to crosscompile here with the following command line:
here's the error log:
a3f1 Answer
You should use the arm-none-linux-gnueabi-
-prefixed toolchain in bin
instead. e.g.
instead of
a3fa3fNot the answer you're looking for? Browse other questions tagged linuxcompiler-errorslinux-kernelarm or ask your own question.
Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Jul 28, 2017
The installation completed without any errors. But when I am trying to compile a Hello World program it gives this message:
But when I try to do the same from the /usr/local/opt/riscv-gcc/bin directory it works fine. |
commented Aug 8, 2017
I'm not able to reproduce this error. Searching online for it suggests a number of possible causes. At first glance, perhaps a permission issue is the most problem? Did you install it with sudo? |
commented Aug 30, 2017
Just to clarify, you shouldn't need to use sudo to install riscv-tools. Homebrew for the last few years hasn't needed sudo. Since there has been no response in 3 weeks, I'm closing this issue. If your problem persists, please comment again to re-open it. |
commented Sep 9, 2017
I'm getting that error while compiling a kernel and still couldn't find a solution :( |
commented Sep 11, 2017
Can you run the following commands to let me know about how it was installed? I'm not able to reproduce this, but re-reading the original issue, I see the original poster has a non-standard Homebrew link directory. In theory it should still work, but gcc can be extremely temperamental about paths. I'm assuming the install used the bottles. Could you also try re-building gcc (will take some time) with |
commented Sep 25, 2017
@madScript01 @Vasu-p Either of you get a chance to double check on this? |
commented Oct 4, 2017
Fixed this, using linaro GCC toolchain and after typing apt-get install aarch64-linux-gnu |
commented Oct 4, 2017
@madScript01 Glad to hear your issues were resolved. Did you experience the issue originally with homebrew on macOS, or were you always using linux (linaro)? |