csound-6.13.0-5.fc32 fails to build in F32:
/usr/bin/ld: CMakeFiles/csbeats.dir/beatslex.yy.c.o:(.bss+0x20): multiple definition of `yyin'; CMakeFiles/csbeats.dir/beats/main.c.o:/builddir/build/BUILD/csound-6.13.0/Frontends/beats/main.c:30: first defined here
collect2: error: ld returned 1 exit status
A difference between passing and failing build root is at
This is probably triggered with an upgrade of gcc from 9.2.1-1.fc32.3 to 10.0.1-0.3.fc32.
This package is tracked by Koschei. See:
csound also fails to build with Python 3.9.0a3.
For the build logs, see:
For all our attempts to build csound with Python 3.9, see:
Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9:
Let us know here if you have any questions.
Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
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 . If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages , 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 ,
any packages not successfully rebuilt at least on Fedora 31 will be
retired regardless of the status of this bug.
FEDORA-2020-b1f037364f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b1f037364f