Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #57874 > unrolled thread

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

Back to article view | Back to linux.debian.kernel

Contents

  Bug#863914: linux-libc-dev: Install separate from /usr/include Zack Weinberg <zackw@panix.com> - 2017-06-01 23:20 +0200
    Processed: Re: Bug#863914: linux-libc-dev: Install separate from  /usr/include owner@bugs.debian.org (Debian Bug Tracking System) - 2017-06-03 23:10 +0200
    Bug#863914: linux-libc-dev: Install separate from /usr/include Ben Hutchings <ben@decadent.org.uk> - 2017-06-03 23:10 +0200
      Bug#863914: linux-libc-dev: Install separate from /usr/include Zack Weinberg <zackw@panix.com> - 2017-06-04 15:20 +0200
        Bug#863914: linux-libc-dev: Install separate from /usr/include Ben Hutchings <ben@decadent.org.uk> - 2017-06-05 02:40 +0200
    Processed: Re: Bug#863914: linux-libc-dev: Install separate from  /usr/include owner@bugs.debian.org (Debian Bug Tracking System) - 2017-06-05 02:40 +0200

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

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, stdarg.h etc)  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.)


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (501, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

[toc] | [next] | [standalone]

#57886 — Processed: Re: Bug#863914: linux-libc-dev: Install separate from /usr/include

Processing control commands:

> tag -1 moreinfo
Bug #863914 [linux-libc-dev] linux-libc-dev: Install separate from /usr/include
Added tag(s) moreinfo.

-- 
863914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863914
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#57889

[Multipart message — attachments visible in raw view] — view raw

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
> their build, other than the kernel's headers and the ones provided by
> the compiler (stddef.h, stdarg.h etc)  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.

Ben.

-- 
Ben Hutchings
Experience is directly proportional to the value of equipment
destroyed.
                                                    - Carolyn Scheppner

[toc] | [prev] | [next] | [standalone]

#57919

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.

zw

[toc] | [prev] | [next] | [standalone]

#57922

[Multipart message — attachments visible in raw view] — view raw

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.

[toc] | [prev] | [next] | [standalone]

#57921 — Processed: Re: Bug#863914: linux-libc-dev: Install separate from /usr/include

Processing control commands:

> tag -1 - moreinfo
Bug #863914 [linux-libc-dev] linux-libc-dev: Install separate from /usr/include
Removed tag(s) moreinfo.

-- 
863914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863914
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web