On Tue, 2012-12-18 at 12:40 -0500, alex lupu wrote: > Apologies in advances (and after). > > At one point I asked questions about this subject. > Many people generously offered valuable help but > to put it bluntly I'm clearly a hopeless case. > The understanding of this topic is obviously way beyond my cognitive > abilities. > So all I'm asking any patient soul here is just to give me > the instructions (army style) about what I have to do now. > > 1. I am at glibc at 2.15 > 2. When I compiled glibc-2.15 (June 15, 2012) I was on 3.3.6 > 3. Subsequently, I installed 3.4.2 > 4. I sanitized things on June 16, 2012 (i.e., a day later) > > For better or for worse, (probably worse) here I am today > (surprisingly, still alive and well) facing this situation: > > 5. Kernel 3.6.9 > 6. I compiled (make, make check) 2.16 successfully. > 7. I haven't done the INSTALL yet expecting instructions/help > to the effect that:
OK, my understanding are that the installed kernel API headers should match those used to build Glibc against. Therefore, my suggestion would be: 1) Build and install your 3.6.9 kernel, including its API headers 2) Build and install Glibc-2.16. 3) Rebuild any BLFS programs you know can take advantage of the updated API headers. Your existing programs will have been built against the old version of Glibc, which itself was built against the old version of the API headers. However, given the backwards compatibility efforts of both projects, I don't think you will notice any breakage, but unless you rebuild BLFS programs you won't also get all the advantages of the additional APIs of either project. Note that I have never done an in place upgrade of Glibc and it used to be advised against, but I think the recent advice is that it should be safe enough. If it breaks though, you get to keep both pieces :) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
