MobileRead Forums - View Single Post

NiLuJe · 09-06-2015, 11:53 AM

@knc1: Yeah, fear of these kinds of things (that, and recent GCC versions plain failing to build old glibcs) were why I initially chose NOT to match exactly the god-awfully ancient K2/K3 toolchain (Linux ~2.6.22, glibc 2.5, GCC 4.2?, IIRC), and instead went with 2.6.27 LTS, glibc 2.9 & an up to date GCC.

I do have to jump through a number of hoops to get buildsystems to play nice and not pull anything newer than GLIBC_2.5, but it's fine for my needs.

If I had to do it all over again, I'd probably go with the 'right' TC, with backported glibc patches as needed to make it build. (I did just that for the Kobo when crosstool-ng dropped eglibc support: the Kobos use eglibc 2_15, which is fine, while on the other hand, mainline glibc 2.15 is horribly broken, so that was fun...).

09-06-2015, 11:53 AM	#49
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@knc1: Yeah, fear of these kinds of things (that, and recent GCC versions plain failing to build old glibcs) were why I initially chose NOT to match exactly the god-awfully ancient K2/K3 toolchain (Linux ~2.6.22, glibc 2.5, GCC 4.2?, IIRC), and instead went with 2.6.27 LTS, glibc 2.9 & an up to date GCC. I do have to jump through a number of hoops to get buildsystems to play nice and not pull anything newer than GLIBC_2.5, but it's fine for my needs. If I had to do it all over again, I'd probably go with the 'right' TC, with backported glibc patches as needed to make it build. (I did just that for the Kobo when crosstool-ng dropped eglibc support: the Kobos use eglibc 2_15, which is fine, while on the other hand, mainline glibc 2.15 is horribly broken, so that was fun...). Last edited by NiLuJe; 09-06-2015 at 11:55 AM.