https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
fiesh at zefix dot tv changed:
What|Removed |Added
CC||fiesh at zefix dot tv
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
chuck cranor changed:
What|Removed |Added
CC||chuck at ece dot cmu.edu
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
--- Comment #4 from Jonathan Wakely ---
Why do you need to use either option? /usr/include is already a system include
dir, so -isystem /usr/include serves no useful purpose.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
--- Comment #5 from chuck cranor ---
I don't think anyone would manually add "-isystem /usr/include" ...
but build systems that provide variables for third party headers that
may or may not be installed in /usr/include often trigger this.
e.g. i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
Shaun Jackman changed:
What|Removed |Added
CC||sjackman at gmail dot com
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
--- Comment #8 from Jonathan Wakely ---
(In reply to chuck cranor from comment #3)
> I think you'll find most build systems that do "-isystem /usr/include"
> instead of "-I /usr/include" are only using "-isystem" for the change
> in the warning b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
Maxim Cournoyer changed:
What|Removed |Added
CC||maxim.cournoyer at gmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
--- Comment #10 from Jonathan Wakely ---
(In reply to Maxim Cournoyer from comment #9)
> About not using it: sure, this works, but now how can a project enable
> warnings just for their own headers and not those of the whole system? This
> seems
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
--- Comment #11 from Maxim Cournoyer ---
(In reply to Jonathan Wakely from comment #10)
> (In reply to Maxim Cournoyer from comment #9)
> > About not using it: sure, this works, but now how can a project enable
> > warnings just for their own hea
11 matches
Mail list logo
