From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.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:52:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1610282044100.31903@digraph.polyomino.org.uk> (raw)
In-Reply-To: <c8ab7e82-63b1-806d-9189-df1af021fe88@redhat.com>
On Fri, 28 Oct 2016, Florian Weimer wrote:
> > 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?
It has limits.h as a wrapper round the libc limits.h. Other headers,
fixed from libc or kernel or other system headers, wouldn't be wanted for
building glibc - but might well be present (and must not be searched until
after glibc's own headers - whereas for limits.h either order is OK).
> Are there any distributions which actually use fixincludes? What would be
If someone has built their own compiler for building glibc I'd expect any
fixed versions of glibc or kernel headers to be there as it would take
special measures to remove them after building GCC.
(I tried before unsuccessfully to get the "#ifdef linux" in linux/a.out.h
which results in it being fixincluded removed.
<https://lkml.org/lkml/2006/10/6/201>
<https://lkml.org/lkml/2011/10/11/210>. Other fixed headers may vary
depending on GCC / glibc / Linux versions.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-10-28 20:52 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
2016-10-28 20:52 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1610282044100.31903@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.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).