Control: tag -1 - moreinfo On Sun, 2017-06-04 at 09:14 -0400, Zack Weinberg wrote: > > On Sat, Jun 3, 2017 at 5:05 PM, Ben Hutchings <ben@decadent.org.uk> wrote: > > > It would be much easier to arrange > > > this if the kernel's headers were installed in a location separate from > > > /usr/include and then symlinked into /usr/include. (It would be fine to > > > symlink just the directories.) > > > > I don't understand how this would help. > > Suppose there exists a directory (let's call it > /usr/src/linux/include, just for concreteness) that contains all the > kernel headers and no other headers. Then my Makefiles can pass > -nostdinc -isystem $(gcc -print-file-name=include) -isystem > /usr/src/linux/include in CFLAGS to see only the kernel's headers and > the compiler's headers. Without such a directory, the only way to get > the same effect that I can think of is to manually create that > directory somehow. It'd be much easier to do this in linux-libc-dev, > which already knows what all the files are. OK, I get it. Ben. -- Ben Hutchings It is easier to write an incorrect program than to understand a correct one.
Attachment:
signature.asc
Description: This is a digitally signed message part