On Tue, 27 Sep 2011 09:22:00 +0200 Victor Martinez <pitillo@crux-arm.nu> wrote: _omissis__
ummmm let's see how can I explain without sound hard. I hope my words aren't picked in a bad sense. About the image, I think it's really good to personal use (may be to make some tests too, but I can't see any good point about it) but not for development purposes, that's why we try to keep the development in git, from toolchain* to *-cross ports. Having the hardfp development done in a image, can give us a
it's fine, don't worry. I choose to release it as image, source and ports archive only to avoid the feeling of "official release" of something other like a fork.
Yeah I understand it, but without knowing about how to replicate it, it's hard for others to start working with it. This is the reason why we try to manage with those "Makefiles", letting others build in their own and look for build problems (or test problems too).
ok, that's just a small abstract about what i did in June to bump from gnueabi (crux arm) to gnueabihf (crux armhf). I hope that my sum-up can help you to "normalize" my work in a Makefile. 1) after a fresh crux arm 2.7-test1 installation (i always worked natively i.e. directly using the efikamx) i bumped the toolchain to gcc-4.6.x and glibc-2.13 here used ports and sources: http://cruxppc.org/~acrux/arm/2.7-SOFT/ports.tar.bz2 http://cruxppc.org/~acrux/arm/2.7-SOFT/src/ 2) i now started from scratch (CLFS way) to bump to gnueabihf that's totally incompatible with gnueabi. Ok, my bad i did't keep a trace of my steps neither i did a Makefile like your ones (i'm lazy and i'm not a coder thus i don't use to write scripts for every kind of task i've in my mind...). Anyway i did like an updated CLFS for ARM. I know i'd have written it as it isn't yet in existence i guess because only now ARM achieved enough strenght and a "desktop status" capable to autonomously build sources. Well this is the point, to bump to gnueabihf i used to do like CLFS that's quite different from a CLFS-sysroot as your standard Makefile does. Or i simply misunderstood your modus operandi and i was in lack of a step using the Makefile approach. Ok, the step that i needed for was to build a temporary system. From CLFS book: [...] The tools in this chapter are cross-compiled using the toolchain in /cross-tools and will be installed under the ${CLFS}/tools directory to keep them separate from the files installed in Installing Basic System Software and the host production directories. Since the packages compiled here are temporary, we do not want them to pollute the soon-to-be CLFS system. [...] After which i was able to succesfully build my full working gnueabihf CLFS system. As i wasn't sure to have a stable system i didn't include graphite support in that toolchain. 3) i transformed that CLFS in a CRUX system. here used ports and sources: http://cruxppc.org/~acrux/arm/2.7-HARD/arm-ports.tar.bz2 http://cruxppc.org/~acrux/arm/2.7-HARD/src/ Well, from CLFS i already choosed to use eglibc as this ARM ABI's flavour is better supported. 4) i updated the system and i added the graphite support (with isl built-in backend). here used ports and sources: http://cruxppc.org/~acrux/arm/2.7-HARD/1/arm-ports.tar.bz2 http://cruxppc.org/~acrux/arm/2.7-HARD/1/update/arm-ports.tar.bz2 http://cruxppc.org/~acrux/arm/2.7-HARD/1/src/ 5) about this toolchain: a stable toolchain for ARM isn't really yet available... http://sourceware.org/ml/binutils/2011-09/msg00162.html http://gcc.gnu.org/ml/gcc/2011-09/msg00361.html cheers, --nico -- acrux <acrux_it@libero.it>