Skip to content
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

-Werror causes build to abort #97

Closed
Leonidas-from-XIV opened this issue Jul 23, 2015 · 5 comments
Closed

-Werror causes build to abort #97

Leonidas-from-XIV opened this issue Jul 23, 2015 · 5 comments

Comments

@Leonidas-from-XIV
Copy link

Hi,

When using the current Fedora 22 default compiler

g++ (GCC) 5.1.1 20150618 (Red Hat 5.1.1-4)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

the build aborts:

Compiling /home/user/project/deps/jiffy/c_src/double-conversion/bignum.cc
/home/user/project/deps/jiffy/c_src/double-conversion/bignum.cc: In member function ‘void double_conversion::Bignum::AssignDecimalString(double_conversion::Vector<const char>)’:
/home/user/project/deps/jiffy/c_src/double-conversion/bignum.cc:101:6: error: assuming signed overflow does not occur when assuming that (X + c) < X is always false [-Werror=strict-overflow]
 void Bignum::AssignDecimalString(Vector<const char> value) {
      ^
cc1plus: all warnings being treated as errors

Removing -Werror lets the build complete sucessfully, with no additional warnings.

@davisp
Copy link
Owner

davisp commented Jul 23, 2015

What version of jiffy are you on? In #89 it was claimed that this was fixed.

@davisp
Copy link
Owner

davisp commented Jul 23, 2015

And the 0.14.1 tag should include that commit if you're still on 0.13.3

@Leonidas-from-XIV
Copy link
Author

I was on 0.13.3, but updating to 0.14.1 did not help since the change in 446e284 was reverted back in 5d6b265.

Reapplying the change in 446e284 does solve the build-warning problem.

@davisp
Copy link
Owner

davisp commented Jul 25, 2015

Doh! My bad. I've submitted the change upstream so hopefully this won't happen again. I'll reapply that patch and tag 0.14.2.

@davisp
Copy link
Owner

davisp commented Aug 31, 2015

Should be fixed now.

@davisp davisp closed this as completed Aug 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants