qucs failed to build from source in Fedora rawhide/f32 https://koji.fedoraproject.org/koji/taskinfo?taskID=41321088 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild Please fix qucs 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, qucs will be orphaned. Before branching of Fedora 33, qucs will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source
Created attachment 1660558 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1660559 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1660560 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Dear Maintainer, your package has not been built successfully in 32. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 33 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 31 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/33/Schedule
It is probably a gcc version 10 collateral effect. I want to try packaging the latest stable release 0.0.19, hopefully solving this problem.
Can't rpmbuild it. I asked some help, and receive a proposal... Need to be implemented
The error message is: gcc -O2 -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=zEC12 -mtune=z13 -fasynchronous-unwind-tables -fstack-clash-protection -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -s -o alter auxfunc_alter.o alter.o auxfunc.o -lm /usr/bin/ld: alter.o:(.bss+0x4): multiple definition of `MPI_EXXIT'; auxfunc_alter.o:(.bss+0x4): first defined here /usr/bin/ld: alter.o:(.bss+0x0): multiple definition of `spice'; auxfunc_alter.o:(.bss+0x0): first defined here /usr/bin/ld: alter.o:(.bss+0x8): multiple definition of `lkk'; auxfunc_alter.o:(.bss+0x8): first defined here /usr/bin/ld: auxfunc.o:(.bss+0x4): multiple definition of `MPI_EXXIT'; auxfunc_alter.o:(.bss+0x4): first defined here /usr/bin/ld: auxfunc.o:(.bss+0x0): multiple definition of `spice'; auxfunc_alter.o:(.bss+0x0): first defined here /usr/bin/ld: auxfunc.o:(.bss+0x8): multiple definition of `lkk'; auxfunc_alter.o:(.bss+0x8): first defined here collect2: error: ld returned 1 exit status This usually happens if more compilation units include the same header file that defines a variable instead of declaring it. Linker then does not know which of the definitions to use. This is triggered by GCC 10.
FEDORA-2020-74cdc3857f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-74cdc3857f
FEDORA-2020-e332fc5cef has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e332fc5cef
FEDORA-2020-e332fc5cef has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e332fc5cef` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e332fc5cef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-74cdc3857f has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-74cdc3857f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-74cdc3857f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-74cdc3857f has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-e332fc5cef has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.