Bug 2045834 - libstoragemgmt: FTBFS in Fedora rawhide/f36
Summary: libstoragemgmt: FTBFS in Fedora rawhide/f36
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libstoragemgmt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tony Asleson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F36FTBFS
TreeView+ depends on / blocked
 
Reported: 2022-01-25 18:39 UTC by Fedora Release Engineering
Modified: 2022-01-26 20:57 UTC (History)
5 users (show)

Fixed In Version: libstoragemgmt-1.9.3-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-26 20:57:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2022-01-25 18:39 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2022-01-25 18:39 UTC, Fedora Release Engineering
no flags Details
state.log (1008 bytes, text/plain)
2022-01-25 18:39 UTC, Fedora Release Engineering
no flags Details
a-repo.s (26.05 KB, application/octet-stream)
2022-01-26 16:08 UTC, Tony Asleson
no flags Details
a-repo.ii (794.42 KB, text/plain)
2022-01-26 16:10 UTC, Tony Asleson
no flags Details
repo.cpp (346 bytes, text/x-csrc)
2022-01-26 16:13 UTC, Tony Asleson
no flags Details

Description Fedora Release Engineering 2022-01-25 18:39:03 UTC
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/

Comment 1 Fedora Release Engineering 2022-01-25 18:39:05 UTC
Created attachment 1855323 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Fedora Release Engineering 2022-01-25 18:39:07 UTC
Created attachment 1855324 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2022-01-25 18:39:08 UTC
Created attachment 1855325 [details]
state.log

Comment 4 Tony Asleson 2022-01-26 16:02:43 UTC
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.

Comment 5 Tony Asleson 2022-01-26 16:08:50 UTC
Created attachment 1855542 [details]
a-repo.s

Comment 6 Tony Asleson 2022-01-26 16:10:22 UTC
Created attachment 1855545 [details]
a-repo.ii

Comment 7 Tony Asleson 2022-01-26 16:13:59 UTC
Created attachment 1855548 [details]
repo.cpp

Comment 8 Tony Asleson 2022-01-26 16:17:48 UTC
Marek should I create an upstream g++ bug submission for this?

Comment 9 Jakub Jelinek 2022-01-26 16:43:59 UTC
It is most likely https://gcc.gnu.org/PR104213

Comment 10 Tony Asleson 2022-01-26 16:52:29 UTC
Thanks Jakub

Comment 11 Marek Polacek 2022-01-26 17:02:36 UTC
Yup, just verified my upstream patch fixes this too.  So it's PR104213 for which I'm going to commit a patch now.


Note You need to log in before you can comment on or make changes to this bug.