From: "Mark Galeck (CW)" <mgaleck@Brocade.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: FW: is "syslimits.h" likely to change?
Date: Thu, 12 Apr 2012 15:39:00 -0000 [thread overview]
Message-ID: <6069BF76D8010446BBF509943DB0D382010D7918EDE9@HQ1-EXCH02.corp.brocade.com> (raw)
In-Reply-To: <mcrwr5la5vt.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
Thank you Ian, hopefully I will be compatible then for a long time, as Larry Wall would say "at least until the heat death of the Universe".
I can't "ignore it" :) My build system cannot handle "include_next" - it cannot handle the situation where you are finding a header file in one -I directory, and later when you are trying to find it again, you ignore that directory and find it in a subsequent -I directory. The system is extremely fast, like a sports car than will only go on asphalt (standard C and a GCC-like compiler).
>I recommend that you simply ignore it in your build system.
next prev parent reply other threads:[~2012-04-12 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 21:03 Mark Galeck (CW)
2012-04-12 5:14 ` Ian Lance Taylor
2012-04-12 15:39 ` Mark Galeck (CW) [this message]
2012-04-13 23:16 ` Dave Korn
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=6069BF76D8010446BBF509943DB0D382010D7918EDE9@HQ1-EXCH02.corp.brocade.com \
--to=mgaleck@brocade.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).