public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/5442] New: Support GCC 4.3's include-fixed directory
Date: Tue, 04 Dec 2007 01:18:00 -0000	[thread overview]
Message-ID: <20071204011820.5442.tschwinge@gnu.org> (raw)

Joseph S. Myers: ``GCC trunk now has multiple internal headers directories, one
containing the self-contained GCC-provided headers and one containing the
<limits.h> (not self-contained but including libc's <limits.h> or a fixed
version thereof) and the fixed headers; more such directories may be added in
future.

When glibc uses -nostdinc, it needs to use -isystem options for all these
internal directories.  This patch teaches it about the include-fixed directory
(and is harmless with old GCC versions without that directory).''

-- 
           Summary: Support GCC 4.3's include-fixed directory
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: tschwinge at gnu dot org
                CC: glibc-bugs at sources dot redhat dot com,joseph at
                    codesourcery dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5442

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2007-12-04  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04  1:18 tschwinge at gnu dot org [this message]
2007-12-04  1:19 ` [Bug libc/5442] " tschwinge at gnu dot org
2007-12-15  9:37 ` ismail at pardus dot org dot tr
2007-12-15  9:37 ` joseph at codesourcery dot com
2008-02-01  0:21 ` cvs-commit at gcc dot gnu dot org
2008-03-29 18:26 ` drepper at redhat dot com

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=20071204011820.5442.tschwinge@gnu.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).