Re: ARM Updates
- Posted by EUWX Apr 03, 2013
- 2763 views
From "Build Error" thread.
I don't fully understand the ARM ecosystem, but there seem to be a lot of different architectures out there, where something built for one chip doesn't work on another, similar to something like i686 vs i386. Then there are the soft vs hard float issues, which are part hardware, part software.
It's probably not as bad as my (poor, incomplete) understanding is, but doing the translation on a more maturely supported (by/for euphoria) platform seems less risky. Of course, it doesn't hurt to try, and if it doesn't work, I don't think it will be subtle, but quick and catastrophic.
Another issue I had was that I couldn't use the cross compiler from my distro, because it linked to GLIBC 2.15, but raspbian uses GLIBC 2.13. I tried several things to hack around this, but couldn't get it to work. The provided cross compilers, OTOH, worked right away with no extra hacks or worrying about setting the right options to target the specific chip, since that was already baked into everything.
For all of these reasons, I suspect that we probably won't be able to offer a single binary ARM distribution of euphoria that we can expect to work everywhere.
Matt
As I said before, Rasbian is still lagging behind officially.
This guy is worth following, but he does not publish his methodology.
http://www.element14.com/community/blogs/mirandasoft/2013/02/19/raspberry-pi-now-running-linux-kernel-380-freshly-compiled-in-the-philippines
You are on the right track with Linaro. They are still going for separate builds, because of the Rapberry Pi guys, but eventually there will be a merged and more generic distro. Eventually you will be able to offer a single binary ARM distro.
