Hi,
I’m trying to find the right toolchain for this image :
bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img
libc6:
Installed: 2.13-38+deb7u10
gcc (Debian 4.6.3-14) 4.6.3
Any idea ? I can’t find it this toolchain :
gcc-linaro-arm-linux-gnueabihf-4.6
Micka,
You need to define what you mean by “toolchain”. Because sudo apt-get install gcc gets you a toolchain on the beaglebone.
Now if you mean a cross compiler toolchain. For 4.6* as far as I can tell you have two options.
It does not seem as though the binaries are available from anywhere any more, but I did not have an exact file name to work with.
That is I could not find a binary for Linaros 4.6.3 gcc toolchain.
Ok, which version of Debian are you using ?
I’m going to switch to this one :
Micka,
william@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2015-03-01
william@beaglebone:~$ uname -r
4.1.14-bone-rt-r17
I’m avoiding Jessie like a plague, for now. Also avoiding systemd. Although the documentation for systemd has much improved over the last year or so. But I’m still not interested. Yet.
Personally, I do not think it matters much which rootfs you run, Jessie or wheezy. This is just a matter of taste. The important part, at least in my mind, is using a 4.1.x kernel.
I agree with you, I’m also on the kernel 4.1.20.
But for cross compilation I have an issue, and I need to find the correct toolchain.
That why I’m going to try Jessy, I hope that I will find easily the toolchain on the linaro webpage.
Micka,
I agree with you, I’m also on the kernel 4.1.20.
But for cross compilation I have an issue, and I need to find the correct toolchain.
That why I’m going to try Jessy, I hope that I will find easily the toolchain on the linaro webpage.
If you can manage to install Ubuntu 14.04 on something, that’s a real solution. Or better yet you can Install Lubuntu 14.04( based on LXDE instead of unity ), which is much faster. Since it uses LXDE instead of Unity. It’ll even run fast in a VM, if thats how you want to run it.
Or you can just do all your compiling natively on the Beaglebone, like I do. I used an NFS share + a ramdisk to keep from compiling on the eMMC or an sdcard.
Anyway, it’s getting late( early ) here so I probably wont respond to any more posts for ~8 hours . . .time to sleep. But I’ll be willing to discuss options with you if you want to stay with a 4.6.3 gcc. After i wake up.
Anyway Micka, if this does not teach you anything else. Learn to keep copies of various things like this that are important for you. I kind of got burnt by this too, but I avoid cross compiling, except for for the kernel. Which Robert has instructions for, and he keeps his instructions updated. Additionally, I really do not see a point any longer to compile my own kernel. Everything I need compiled in, is.
Hi,
I can’t compile on the beaglebone black because there is too much source to compile. On a VM, the cross compile goes very fast !
I’ve tried to cross compile with ubuntu 12.4.5 , but it looks like that I don’t have the same lib on ubuntu :
beagle :
ldd --version /lib/arm-linux-gnueabihf/libgcc_s.so.1
ldd (Debian EGLIBC 2.13-38+deb7u10) 2.13
ubuntu:
ldd --version /usr/arm-linux-gnueabihf/lib/libgcc_s.so.1
ldd (Ubuntu EGLIBC 2.15-0ubuntu10.13) 2.15
I’ve to try and find the correct toolchain (_(
any idea ? can I copy all file in the beagle and copy in the ubuntu folder.
beagle /lib/arm-linux-gnueabihf to ubuntu /usr/arm-linux-gnueabihf/lib/
??
Well,
I’m going to make my own toolchain ! Let’s have fun lol !
http://hansbot.blogspot.fr/p/beaglebone-black-mac-os-x-toolchain.html
http://bettercommute.org/emblinux/projects/fall2013/Project_beagleboard_Aditya.pdf
From those link, it doesn’t looks like that difficult !
The important information are :
root@beaglebone:~# ldd --version
root@beaglebone:~# cat /proc/version
root@beaglebone:~# gdb --version
and with that you configure and make your toolchain ^^
Take a look at:
https://github.com/RobertCNelson/cross-compiler/blob/master/build-wheezy-compiler.sh
BUT, you need to be running Debian wheezy on your x86 host...
It's been two years since i last played around with it, so it'll probally
need package version updates..
Regards,
Micka,
You should be able to link against whichever libraries you want when compiling whatever. It’s been a long while since I’ve actually done this myself, so i do not remember how. toolchains usually have a way to add paths, and/or libraries.
Just browsing through Roberts script there . . . assuming what he says is true. One could be in for a lot of work. Changing version numbers by hand in the script . . . 
Pretty cool script though.
Things got a little easier in jessie (and stretch will be more easier):
https://wiki.debian.org/CrossToolchains#In_jessie_.28Debian_8.29
Regards,
Things got a little easier in jessie (and stretch will be more easier):
https://wiki.debian.org/CrossToolchains#In_jessie_.28Debian_8.29
Regards,
One of the redeeming qualities of Ubuntu. This has been possible in Ubuntu for a couple years now . . . However, I’d hate to have to try and figure out how to adapt your guide to using a built in apt-gettable package though . . .hehe.
That is to say. I know it’s possible, and I’m pretty sure I could do it. But that sure would be one hell of an aggravation fest . . .
Yeah, it missed the freeze window for jessie, so it got held back for 2
years. 
Regards,
I was just reading that link you gave Robert. This kind of makes sense, but is a bit confusing. How could this build a cross kernel ?
I guess what I’m confused about is: Is that actually a native compiler executable ?