Description of problem: Building R modules using the latest R built in rawhide fails because the saved linking flags from the R build contains -Wl,-dT,/builddir/build/BUILD/R-4.1.2/.package_note-R-4.1.2-2.fc36.x86_64.ld. This file existed during the build of them main R package, but not when building R modules against it. Version-Release number of selected component (if applicable): R-core-devel-4.1.2-2.fc36 How reproducible: Always Steps to Reproduce: 1. Build an R rmodule that compiles code against the latest R in rawhide. Actual results: /usr/bin/ld: cannot open linker script file /builddir/build/BUILD/R-4.1.2/.package_note-R-4.1.2-2.fc36.x86_64.ld: No such file or directory collect2: error: ld returned 1 exit status Expected results: No error. Additional info: Seen by failing builds in koschei, e.g. https://koji.fedoraproject.org/koji/taskinfo?taskID=81931021
Where does this package_note come from? Is this part of a change for F36?
It comes from redhat-rpm-config. It is a new feature in F36. It causes problems for other packages that keeps track of build flags too for building modules, like ruby and python. You can check what was donr there.
Applying the same "fix" that ruby uses. Build going now.
If they are EPEL-compatible, a possible solution would be to use %{extension_*flags} [1]. Reading the devel thread and related bugs, I understood that this is what Python uses and it's Miro's proposal for Ruby too. [1] https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/rawhide/f/buildflags.md#support-for-extension-builders
R-4.1.2-3.fc36 should no longer have this issue.