This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Nov 30, 2004, Al Viro <viro@parcelfarce.linux.theplanet.co.uk> wrote: > WTF? I've got a dozen kernel trees hanging around, which one (and WTF any, > while we are at it) should be "linked to"? Whichever you chose to install in your /usr/include, and use as the kernel ABI definition as far as userland is concerned. I don't think `make install' should touch /usr/include at all. It should be a separate step, such that one can build a kernel abi headers package out of the kernel source tree, ideally without even having to configure it first, and use that as the kernel ABI definition. You should only have to do this again *if* the ABI changes (ideally no removals, only additions) *and* you want to take advantage of them, *and* you're willing to rebuild userland pieces that could take advantage of them. On most systems, people won't do that, they'll just use whatever kernel headers and glibc binaries their distro ships. If they want to change any of these, they have to know what they're doing. -- Alexandre Oliva http://www.ic.unicamp.br/~oliva/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |