On Thursday 09 September 2010, walt wrote: > On 09/09/2010 09:26 AM, Volker Armin Hemmann wrote: > > On Thursday 09 September 2010, walt wrote: > >> And the only reason to re-compile an existing glibc is if the linux > >> kernel headers change. I always re-compile glibc when the linux kernel > >> headers change... > > > > hm, I never recompile glibc after a header update.... or anything > > else.... > > I never did either until recently, when I started playing with vbox from > its svn repository in addition to tracking the latest from Linus.git. > > Until then I had no idea how often the kernel devs break things by changing > kernel data structures and system calls without notice.
system calls are never changed. And kernel structures are irrelevant for userspace. So if you don't use any modules, you don't have to recompile anything. In fact, glibc's own header set are derived from some very acient kernel headers.
