Syntastic reports error with GCC 6.1

21 views
Skip to first unread message

Thomas R.

unread,
May 25, 2016, 2:24:21 PM5/25/16
to vim-syntastic


Hi,

After upgrading my system (Arch Linux, Vim 7.4, GCC 6.1) , Syntastic complains about stuff in the include folder of c++, is there something I am doing wrong here? Thank you in advance














LCD 47

unread,
May 25, 2016, 2:52:51 PM5/25/16
to vim-syntastic
> <https://lh3.googleusercontent.com/-4yvOm0z7Bc0/V0XtTlvH5nI/AAAAAAAADh4/98IqmFOMoSQw1Uj3GwZb9Np6KdLwSMX6QCLcB/s1600/2016-05-25-201102_1920x1080_scrot.png>

Syntastic doesn't care about the contents of the files it checks.
It runs external programs against your files, parse their output, and
shows you the results in a window. As such, it can at worst omit error
messages produced by compilers (presumably because it didn't parse them
correctly), but it can never "invent" error messages that were not
in the output of some compiler. If you're seeing messages you don't
expect, they have been produced by gcc, not by sintastic.

To see how syntastic runs gcc enable debugging and look for
"makeprg" in the output (see ":h syntastic-config-debug").

To change the way syntastic runs gcc set the relevant checker
options. Read ":h syntastic-config-makeprg", and the wiki entry for
gcc:

https://github.com/scrooloose/syntastic/wiki/C--%3A---gcc

If the errors shown by syntastic don't correspond to the output of
gcc when run with the same options in a terminal, please open an issue
at the issue tracker:

https://github.com/scrooloose/syntastic/issues

/lcd

Thomas R.

unread,
May 25, 2016, 5:02:41 PM5/25/16
to vim-syntastic
Thanks a lot for the explanation, I found that the -std=gnu++98 flag was missing from my syntastic config file.
Reply all
Reply to author
Forward
0 new messages