From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Add test for linking against most static libraries
Date: Fri, 28 Oct 2016 20:27:00 -0000 [thread overview]
Message-ID: <c8ab7e82-63b1-806d-9189-df1af021fe88@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1610282002550.31903@digraph.polyomino.org.uk>
On 10/28/2016 10:07 PM, Joseph Myers wrote:
> On Fri, 28 Oct 2016, Florian Weimer wrote:
>
>> I suspect the only way to guard against this is to parse the default compiler
>> search paths from gcc -v and replace the variants of /usr/include found
>> therein with a carefully prepared directory tree of installed headers and some
>> linked-in kernel headers.
>
> Building glibc needs compiler headers (include and include-fixed
> directories - but while we need limits.h from include-fixed, there may be
> other headers in include-fixed that we don't want) and kernel headers.
Are you certain about include-fixed part?
Are there any distributions which actually use fixincludes? What would
be found there?
We need quite a few headers from GCC (even more with C++), but I'd
suggest to rewrite the default include path to strip /usr/include,
/usr/local/include and the multi-arch header directories if applicable,
and leave the GCC include directories in place. The glibc installed
header directory would take the place where /usr/include originally was.
> But in some cases it may require other installed system headers as well.
> E.g. memusagestat requires installed GD headers. Systemtap support
> requires installed sys/sdt.h. I don't know what might require other
> installed headers as well, especially for the non-Linux ports.
True. NSS is another problematic case.
> So while avoiding /usr/include is desirable, doing so while keeping all
> the cases that properly use installed headers working may be tricky.
Yes, but a cleaner separation seems desirable to me.
> (I'd argue that the memusagestat case should be solved by moving it to a
> separate package - maybe released along with glibc, but built with
> installed libraries only rather than as part of a glibc build.)
Seems reasonable.
I'm also trying to phase out NSS-based libcrypt at Red Hat, or
alternatively, convince a real cryptographic library to build the
library for us.
Thanks,
Florian
next prev parent reply other threads:[~2016-10-28 20:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 12:57 Florian Weimer
2016-10-28 14:51 ` Carlos O'Donell
2016-10-28 17:30 ` Carlos O'Donell
2016-10-28 17:33 ` Joseph Myers
2016-10-28 17:42 ` Florian Weimer
2016-10-28 17:48 ` Joseph Myers
2016-10-28 18:30 ` Carlos O'Donell
2016-10-28 20:16 ` Carlos O'Donell
2016-10-28 20:22 ` Joseph Myers
2016-10-29 2:41 ` Carlos O'Donell
2016-10-28 18:55 ` Florian Weimer
2016-10-28 20:08 ` Joseph Myers
2016-10-28 20:27 ` Florian Weimer [this message]
2016-10-28 20:52 ` Joseph Myers
2016-10-28 20:21 ` Carlos O'Donell
2016-10-28 18:27 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c8ab7e82-63b1-806d-9189-df1af021fe88@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).