-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get glib to compile with gcc-6.1 #997
Conversation
This commit adds a patch to fix the case where gcc-6.1 emits an error for string format literal that was a warning in previous versions of gcc. The patch reference is https://bugzilla.gnome.org/show_bug.cgi?id=761550 Also ran the package file through autopep8.
It looks like there may be a problem with the travis check itself. The failure that I see, for only the python-2.6 test is:
That seems unrelated to any changes made in this PR. |
Hmm, yeah, seems that something went south inside of |
@mathstuf I am not seeing that happen here. |
Was analyzing the error output from the tests :) . I agree it is likely not something that's an issue with the branch. |
@mathstuf Sorry, I had forgotten about the test errors. The email updates do not provide enough (any) context. Thanks. |
Ah, missed that the error had occurred 2+ weeks ago :) . Yep, would have quoted more if I had realized that. |
Sigh. This works for GCC, but clang is obstinate and still errors out on it :( . |
This commit adds a patch to fix the case where gcc-6.1 emits an error
for string format literal that was a warning in previous versions of
gcc. The patch reference is
https://bugzilla.gnome.org/show_bug.cgi?id=761550
Also ran the package file through autopep8.