Hi,
I'm hoping that someone on this list can say "Oh, ya, this change
happened and it causes that, here's the solution." because I've spent a
month running against a brick wall.
Short summary:
rubygem-passenger won't build due to uint32_t issues. And it is
affecting x86_64 different than it is i386 and arm.
Details:
With original src.rpm, x86_64 build [1] failed with the error
"error: 'uint8_t' does not name a type"
and
"error: 'uint32_t' does not name a type"
With original src.rpm, i386 build [2] failed with the error
"error: reference to 'uint32_t' is ambiguous"
With a patch that puts "#include <stdint.h>" into the correct header
files, x86_64 builds correctly.[3]
But that patch does nothing for i386 or arm build. [4]
So, my question is this.
What happened with f20 that causes these errors?
What is a good way to track down a solution to "error: reference to
'uint32_t' is ambiguous"?
Thanks
Troy Dawson
[1] http://kojipkgs.fedoraproject.org//work/tasks/1540/5951540/build.log
[2] http://kojipkgs.fedoraproject.org//work/tasks/1545/5951545/build.log
[3] http://kojipkgs.fedoraproject.org//work/tasks/2733/5952733/build.log
[4] http://kojipkgs.fedoraproject.org//work/tasks/2735/5952735/build.log
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
