Bug 1943031 - lordsawar: FTBFS with upcoming autoconf-2.71
Summary: lordsawar: FTBFS with upcoming autoconf-2.71
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lordsawar
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bruno Wolff III
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1942967
TreeView+ depends on / blocked
 
Reported: 2021-03-25 12:45 UTC by Ondrej Dubaj
Modified: 2021-07-30 15:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-07-30 15:45:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ondrej Dubaj 2021-03-25 12:45:10 UTC 
Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test
Comment 1 Ondrej Dubaj 2021-04-12 07:13:22 UTC 
Gentle ping.
Comment 2 Bruno Wolff III 2021-04-12 17:26:03 UTC 
I don't think the problem is related to autoconf. It looks like there are some errors in a library used by lordsawar that might not have been flagged in earlier versions of gcc. At least that issue should be fixed first.
Comment 3 Ondrej Dubaj 2021-05-04 07:49:04 UTC 
Hi, are there any updates to this issue ?

Thanks.
Comment 4 Bruno Wolff III 2021-05-04 15:45:29 UTC 
I don't think the FTBFS is related to autoconf.
I did notice a new cause as rpmbuild seems to have gotten pickier about macros in comments. I pushed a fix to master for that.
I think the real problem is probably in gstreamermm possibly do too a gcc update. Right now I'm hoping that gets fixed there as looking into why errors are being flagged in the c++ include file is not an area I'm very good at.
Comment 5 Ondrej Dubaj 2021-05-04 17:43:00 UTC 
Thanks for keeping us informed.
Comment 6 Bruno Wolff III 2021-07-30 15:45:20 UTC 
It looks like the dependency got fixed.
Note You need to log in before you can comment on or make changes to this bug.