Summary: | dev-libs/protobuf (any version) fails to build with -march=ivybridge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Xavier Miller <xavier.miller> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | dan, luke5083, marek.duranik, negril.nx+gentoo, reuben-gentoo-bugzilla, sam, xavier.miller |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 914580 | ||
Attachments: | build.log |
Description
Xavier Miller
2024-06-15 08:07:09 UTC
Created attachment 895873 [details]
build.log
seems related to abseil-cpp but I tried with older versions without any success I wonder if this is actually caused by gcc-14: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789 I have the same build problem and I am on the same gcc build too. But I'm not on an ivybridge processor, on a CPU type of: "KVM Processor v2.0" and the underlying processor as shown in /proc/cpuinfo is an AMD. (In reply to Reuben Farrelly from comment #3) > I wonder if this is actually caused by gcc-14: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789 > > I have the same build problem and I am on the same gcc build too. But I'm > not on an ivybridge processor, on a CPU type of: "KVM Processor v2.0" and > the underlying processor as shown in /proc/cpuinfo is an AMD. I think the problem is really related to the processor feature requested by protobuf, but not enabled in Intel Ivy Bridge family if I dump -march=native and -mtune=native, I got -mno-lzcnt in the options. but even if I add -mno-lzcnt in CFLAGS and rebuild abseil-cpp, protobuf fails because it ask this function that will not work for me. I filed a bug at protobuf's GitHub Given we're quite far behind with versions in Gentoo (it's a mess and someone is working on it), I wouldn't assume it's not fixed already upstream. The code changed in https://github.com/protocolbuffers/protobuf/commit/7315f6d398d2d18443b26c513cbdcdbffaeebaa3 at least. (In reply to Sam James from comment #6) > Given we're quite far behind with versions in Gentoo (it's a mess and > someone is working on it), I wouldn't assume it's not fixed already upstream. > > The code changed in > https://github.com/protocolbuffers/protobuf/commit/ > 7315f6d398d2d18443b26c513cbdcdbffaeebaa3 at least. Hi, Sam! I did not check that Gentoo in ~arch used a so outdated package... The patch you link is not sufficient, need more patches or a more recent protobuf release. I can build protobuf 21.12 Hi Xavier! Thank you for trying to do the right thing as well, not your fault at all, hopefully we can get abseil+protobuf sorted out on our side soon. (In reply to Reuben Farrelly from comment #3) > I wonder if this is actually caused by gcc-14: FTR I have just tested this: gcc-13 (Gentoo Hardened 13.3.1_p20240614 p17) 13.3.1 20240614 - protobuf 23.3-r4 builds successfully gcc-14 (Gentoo Hardened 14.1.1_p20240615 p2) 14.1.1 20240615 - protobuf 23.3-r4 fails to build. It is a workaround at least for anyone who runs into the same problem and finds this bug report. |