Op 9 aug. 2011, om 17:29 heeft Khem Raj het volgende geschreven: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/09/2011 01:38 AM, Koen Kooi wrote: >> Hi, >> >> For angstrom-core we currently have the following configs: >> >> 2011.x: gcc: 4.5.x binutils: 2.20.x eglibc: 2.12 >> >> bleeding: gcc: 4.6.x binutils: 2.21.x eglibc: 2.13 >> >> With the october release of OE-core coming up it makes a lot of sense >> to start thinking of the toolchain roadmap. Do we want to keep the >> current one and move the bleeding into the master config after the >> release or do we want to update e.g. eglibc to 2.13 before the >> release. >> >> And better ideas for release names and numbers are appreciated as >> well. > > I think. We can use eglibc 2.13 release. Since 2.13 has been tested > quite a bit and does not have any radical features it should be > relatively safe. > > I would propose bintutils 2.21.x as well if there is no dependency on > 2.20.x anymore but its medium risk
2.21.x breaks with 'old' kernels on armv7a, so I'd like to have the october release work with those and introduce the breakage after that. _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
