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

capnproto 0.5.3 FTBFS on GCC 7 for Fedora 26 (RHBZ#1423291) #418

Closed
Conan-Kudo opened this issue Feb 22, 2017 · 4 comments
Closed

capnproto 0.5.3 FTBFS on GCC 7 for Fedora 26 (RHBZ#1423291) #418

Conan-Kudo opened this issue Feb 22, 2017 · 4 comments

Comments

@Conan-Kudo
Copy link
Contributor

During the development of Fedora 26, we've done a mass rebuild in accordance with the work to switch the distribution to GCC 7.

However, capnproto 0.5.3 fails to build on GCC 7 (gcc 7.0.1).

This is the error that repeats itself throughout the build run, with some variation based on the file in the make thread (run at make -j48):

In file included from src/capnp/list.h:29:0,
                 from src/capnp/list.c++:22:
src/capnp/layout.h:129:65: error: could not convert template argument 'b' from 'bool' to 'capnp::Kind'
 template <typename T, bool b> struct ElementSizeForType<List<T, b>> {
                                                                 ^
src/capnp/layout.h:129:66: error: template argument 1 is invalid
 template <typename T, bool b> struct ElementSizeForType<List<T, b>> {
                                                                  ^~

Full build logs are available at the Red Hat Bugzilla bug.

@Omnifarious
Copy link

Omnifarious commented Feb 25, 2017

I tried using the latest gcc from rawhide, and I didn't get those errors. It built fine. But capnproto crashed.

I used the fedora:rawhide Docker container on a Fedora 25 host.

@Omnifarious
Copy link

$ ./capnp compile -oc++ src/capnp/test.capnp
*** Received signal #11: Segmentation fault
stack: 0x7fe469a08b65 0x7fe469a0a2fb 0x7fe469a0b444 0x7fe469a0b444 0x7fe469a0c516 0x4081fd 0x7fe469a57811 0x7fe469a5790b 0x7fe469a57e39 0x7fe469a57e74 0x40c1e8 0x7fe46954770a 0x7fe469548acb 0x7fe46953a988 0x7fe469549445 0x405dc1 0x7fe4686a55fe 0x405e9a

@kentonv
Copy link
Member

kentonv commented Feb 27, 2017

I believed this was fixed in master by 0f1fd19. You can cherry-pick that into your package if needed.

@kentonv kentonv closed this as completed Feb 27, 2017
@kentonv
Copy link
Member

kentonv commented Feb 27, 2017

@Omnifarious You seem to be describing a separate bug. Could you file a separate issue?

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

No branches or pull requests

3 participants