On Tue, Aug 05, 2008 at 07:26:07PM +0100, Jamie Lokier wrote: >> > >The userspace headers are independent of any kernel configuration >> > >(except for the architecture). >> > >> > I beg to disagree: >> > internals as exposed by e.g. aio_abi.h are impl dependent. Noone except >> > the impl and it's users are interrested in it. >> >... >> >> That's utter bullshit. >> >> The contents of aio_abi.h is a kernel<->userspace ABI that mustn't ever >> change. [1] > >Case in point: > >I want to be able to compile an application for embedded Linux which >*can use* Linux-AIO, but can also run on a kernel which has Linux-AIO >removed by this patch. > >I still want to compile the application with that capability, in case >it's run on another kernel with it enabled. > >I shouldn't have to have a separate, special kernel with all options >enabled, just to compile applications that run on multiple kernels and >use run-time features when available. > >Just like all the other kernel<->userspace interfaces, the header >files (including their presence) shouldn't depend on kernel >configuration at all. alright, makes perfect sense. I must have been playing too much with libc recently, i guess. thanks, -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
