> >> features.h is included by almost every glibc header and contains some > >> basic information. Without features.h you cannot use glibc at all. > >> Without having loked at your environment, I would say add it. > > > > I don't this that will be neccessary. The LSB sort of defines one particular > > set of values for the things in features, so the rest of the headers are > > "hard coded" to those features. They don't need to include features.h to > > figure anything out. > > As I've said, I didn't look at the LSB headers so far... > > Currently <features.h> does the following: > - include <sys/cdefs.h> > - defines all sort of defines > > The only reason I see directly to include <features.h> directly by an > application is to get the values of __GLIBC__ and __GLIBC_MINOR__ if > no other include file is used - but that's quite academical.
configure scripts through config.guess includes features.h directly to work out the version of glibc. So I think we should be providing something here for them, or a lot of packages will need some fiddling to get them to compile. Chris. -- [EMAIL PROTECTED] IBM OzLabs Linux Development Group Canberra, Australia
