From: Pedro Alves <palves@redhat.com>
To: Paul_Koning@dell.com, schwab@suse.de
Cc: gdb@sourceware.org
Subject: Re: Why pedantic?
Date: Tue, 25 Aug 2015 13:41:00 -0000 [thread overview]
Message-ID: <55DC7097.5080704@redhat.com> (raw)
In-Reply-To: <9F3A813A-9CB4-4B8B-9D4F-7E687B95834C@dell.com>
On 08/25/2015 02:17 PM, Paul_Koning@dell.com wrote:
>
>> On Aug 25, 2015, at 9:05 AM, Andreas Schwab <schwab@suse.de> wrote:
>>
>> <Paul_Koning@Dell.com> writes:
>>
>>> The problem is that the libiberty build, as is typical, uses header files from the host, and there is no reason to assume that all those headers on every supported host OS are pedantic-safe.
>>
>> GCC suppresses warnings in system headers by default.
>
> For cross-builds? Not in the ones we do. Is there some command line switch that needs to be passed to tell gcc that a particular include directory is for "system headers" and to apply that rule?
-isystem instead of -I.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-08-25 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 18:15 Paul_Koning
2015-08-25 10:05 ` Pedro Alves
2015-08-25 12:52 ` Paul_Koning
2015-08-25 13:05 ` Andreas Schwab
2015-08-25 13:17 ` Paul_Koning
2015-08-25 13:41 ` Pedro Alves [this message]
2015-08-25 13:44 ` Andreas Schwab
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=55DC7097.5080704@redhat.com \
--to=palves@redhat.com \
--cc=Paul_Koning@dell.com \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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