-
-
Notifications
You must be signed in to change notification settings - Fork 419
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
Unable to create Fedora releases due to compilation error #3313
Comments
I think gcc 8.1 along with the |
It's unclear to me whether this is a real bug or not (the compiler thinks it is). I assume from a quick glance that it is, but we'd need to verify that. |
@jemc i'm not familiar with what is going on with the AST. Is this an actual error? |
I get a 404 error when I click the link to see the build log. Do you have a copy of the error location and message? |
Ugh. Apparently the build log gets deleted after a week. It's gone. Building with gcc 8.1 should do the trick. There's a warning about strncpy at 3 locations in verify.c. The warning to use to see it is: "-Werror=stringop-truncation" |
I have this error on
|
An option to fix for now would be:
It doesn't verify if the warning is real or not (this need to look at that, but it should in theory, put gcc 8+ compilation on the same footing as all the others in that it will build. |
N.B. its quite possible that some of these are false positives. |
Yeah, these look like false positives. |
Starting with GCC 8, they added a new warning `stringops-truncation`. It is well intentioned but, seems prone to a lot of false positives. It found several false positives in the Pony codebase and because we treat all warnings as errors, you can't build ponyc with GCC 8+. This commit turns off the new warning and returns us to a state of bliss. Fixes #3313
Starting with GCC 8, they added a new warning `stringops-truncation`. It is well intentioned but, seems prone to a lot of false positives. It found several false positives in the Pony codebase and because we treat all warnings as errors, you can't build ponyc with GCC 8+. This commit turns off the new warning and returns us to a state of bliss. Fixes #3313
Using Ubuntu Xenial and Gcc 8.3, I am unable to reproduce this. Very odd. |
Starting with GCC 8, they added a new warning `stringops-truncation`. It is well intentioned but, seems prone to a lot of false positives. It found several false positives in the Pony codebase and because we treat all warnings as errors, you can't build ponyc with GCC 8+. This commit switches from using strncpy to memcpy. They are in the end, the same operation except a difference in return type. However, with the new gcc option, memcpy will not complain about not copying the null terminator. Fixes #3313
Starting with GCC 8, they added a new warning `stringops-truncation`. It is well intentioned but, seems prone to a lot of false positives. It found several false positives in the Pony codebase and because we treat all warnings as errors, you can't build ponyc with GCC 8+. This commit switches from using strncpy to memcpy. They are in the end, the same operation except a difference in return type. However, with the new gcc option, memcpy will not complain about not copying the null terminator. Fixes #3313
Fedora COPR builds changed the warnings they have on or otherwise changed the gcc version and ponyc no longer compiles. We need to fix this to get COPR builds working again.
See: https://copr-be.cloud.fedoraproject.org/results/ponylang/ponylang/fedora-29-x86_64/01042125-ponyc/build.log.
What we need to do:
the 2nd 2 steps should be part of the same PR.
The text was updated successfully, but these errors were encountered: