Bug#863914: linux-libc-dev: Install separate from /usr/include

2017-06-04 Thread Ben Hutchings
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 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

Bug#863914: linux-libc-dev: Install separate from /usr/include

2017-06-04 Thread Zack Weinberg
On Sat, Jun 3, 2017 at 5:05 PM, Ben Hutchings 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

Bug#863914: linux-libc-dev: Install separate from /usr/include

2017-06-03 Thread Ben Hutchings
Control: tag -1 moreinfo On Thu, 2017-06-01 at 17:14 -0400, Zack Weinberg wrote: > Package: linux-libc-dev > Version: 4.11-1~exp2 > Severity: wishlist > > Certain low-level programs and libraries, notably glibc, would like to > be able to make sure that they do *not* use any system headers during

Bug#863914:

2017-06-01 Thread Zack Weinberg
Upstream patch submission: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1411004.html

Bug#863914: linux-libc-dev: Install separate from /usr/include

2017-06-01 Thread Zack Weinberg
Package: linux-libc-dev Version: 4.11-1~exp2 Severity: wishlist Certain low-level programs and libraries, notably glibc, would like to be able to make sure that they do *not* use any system headers during their build, other than the kernel's headers and the ones provided by the compiler (stddef.h,