libstoragemgmt failed to build from source in Fedora rawhide/f36 https://koji.fedoraproject.org/koji/taskinfo?taskID=81787645 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild Please fix libstoragemgmt at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, libstoragemgmt will be orphaned. Before branching of Fedora 37, libstoragemgmt will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Created attachment 1855323 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1855324 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1855325 [details] state.log
This maybe a compiler issue. The package is failing to build because a compile warning is being generated for armv7hl only and the package treats warnings as errors. The following reproduces the warning that doesn't occur for other compiled architectures on fedora: $ uname -m armv7l $ cat repro.cpp #include <iostream> #include <stdexcept> class SomeException : public std::runtime_error { public: SomeException(std::string m) : std::runtime_error(m) {} }; int main() { try { throw SomeException("compiler bug?"); } catch (const SomeException &e) { std::cout << e.what() << std::endl; } return 0; } $ g++ -Wall repo.cpp -save-temps repo.cpp: In destructor ‘virtual SomeException::~SomeException()’: repo.cpp:4:7: warning: pointer used after ‘void operator delete(void*, std::size_t)’ [-Wuse-after-free] 4 | class SomeException : public std::runtime_error { | ^~~~~~~~~~~~~ repo.cpp:4:7: note: call to ‘void operator delete(void*, std::size_t)’ here To get the builds working again, I'll likely remove `-Werror` for the package build.
Created attachment 1855542 [details] a-repo.s
Created attachment 1855545 [details] a-repo.ii
Created attachment 1855548 [details] repo.cpp
Marek should I create an upstream g++ bug submission for this?
It is most likely https://gcc.gnu.org/PR104213
Thanks Jakub
Yup, just verified my upstream patch fixes this too. So it's PR104213 for which I'm going to commit a patch now.