Public bug reported: frr was placed in lto-disabled-list because it failed to build[1] in the first round of lto testing, but turns out that failure is not lto related:
checking python interpreter python3... /usr/bin/python3 (python3) checking whether /usr/bin/python3.9-config is available... yes checking whether /usr/bin/python3.9-config provides a working build environment... no checking whether pkg-config python-3.9 is available... yes checking whether pkg-config python-3.9 provides a working build environment... no checking whether /usr/bin/python3.9-config is available... yes checking whether /usr/bin/python3.9-config provides a working build environment... no checking whether pkg-config python-3.9 is available... yes checking whether pkg-config python-3.9 provides a working build environment... no configure: error: PYTHON (/usr/bin/python3) explicitly specified but development environment not working I just tried a rebuild of frr 8.1 from jammy, with lto enabled, and it built fine, therefore we can remove it from the lto-disabled-list package. 1. https://launchpadlibrarian.net/519568994/buildlog_ubuntu-hirsute-amd64.frr_7.4-1_BUILDING.txt.gz ** Affects: frr (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959838 Title: Rebuild with lto enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/frr/+bug/1959838/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
