Bug 2070099 - rakudo-0.2020.07-4.fc37 FTBFS: /usr/bin/ld: cannot open linker script file /builddir/build/BUILD/.package_note-moarvm-0.2020.07-5.fc36.x86_64.ld: No such file or directory
Summary: rakudo-0.2020.07-4.fc37 FTBFS: /usr/bin/ld: cannot open linker script file /b...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rakudo
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F36FTBFS F37FTBFS
TreeView+ depends on / blocked
 
Reported: 2022-03-30 12:29 UTC by Petr Pisar
Modified: 2022-07-05 16:37 UTC (History)
4 users (show)

Fixed In Version: moarvm-0.2020.07-6.fc37 rakudo-0.2020.07-5.fc37 rakudo-0.2020.07-5.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 16:37:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2022-03-30 12:29:55 UTC
rakudo-0.2020.07-4.fc37 fails to build in Fedora 37:

+ /usr/bin/perl Configure.pl --prefix=/usr --backends=moar
Can't exec "git": No such file or directory at Configure.pl line 16.
Can't exec "git": No such file or directory at Configure.pl line 23.
Can't exec "git": No such file or directory at Configure.pl line 24.
Using /usr/bin/nqp-m (version 2020.07 / MoarVM 2020.07).
Cleaning up ...
You can now use 'make' to build Rakudo.
After that, 'make test' will run some tests and
'make install' will install Rakudo.
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64  -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
+ make -j6
+++ Checking for moar NQP version
+++ Expanding	gen/moar/main-version.nqp
Can't exec "git": No such file or directory at /builddir/build/BUILD/rakudo-2020.07/Configure.pl line 16.
Can't exec "git": No such file or directory at /builddir/build/BUILD/rakudo-2020.07/Configure.pl line 23.
Can't exec "git": No such file or directory at /builddir/build/BUILD/rakudo-2020.07/Configure.pl line 24.
+++ Generating	gen/moar/rakudo.nqp
+++ Generating	gen/moar/Grammar.nqp
+++ Generating	gen/moar/World.nqp
+++ Generating	gen/moar/ModuleLoader.nqp
+++ Compiling	blib/Perl6/ModuleLoader.moarvm
+++ Generating	gen/moar/Ops.nqp
+++ Compiling	dynext/libperl6_ops_moar.so
/usr/bin/ld: cannot open linker script file /builddir/build/BUILD/.package_note-moarvm-0.2020.07-5.fc36.x86_64.ld: No such file or directory
collect2: error: ld returned 1 exit status
make: *** [Makefile:1219: dynext/libperl6_ops_moar.so] Error 1

A difference between passing and failing build root is at <https://koschei.fedoraproject.org/build/11954424>. This is probably triggered by upgrading redhat-rpm-config from 211-1.fc36 to 212-1.fc36 (Add package note generation to %check preamble; bug #2043977).

Comment 1 Xose Vazquez Perez 2022-05-29 17:00:18 UTC
(In reply to Petr Pisar from comment #0)

> rakudo-0.2020.07-4.fc37 fails to build in Fedora 37:

raku stack in Fedora is 2 years old, maybe it should be updated:
https://src.fedoraproject.org/rpms/rakudo
https://src.fedoraproject.org/rpms/moarvm
https://src.fedoraproject.org/rpms/nqp

Comment 2 Petr Pisar 2022-06-08 13:21:59 UTC
The cause of this failure is that moarvm package builds in compiler flags which refer to the .package_note-moarvm... file. Then rakudo build script retrieves the flags from moarvm and applies them to itself. Obviously a file generated by Fedora build systme for moarvm sources does not exist in rakudo sources. This needs a fixes in moarvm. Not in rakudo. I don't believe that this issue is resolved in a newer moarvm. This problem is common to various language compilers and usually do not care about it. A simple work around is disabling package note feature in moarvm.spec.

Comment 3 Fedora Update System 2022-06-24 13:26:00 UTC
FEDORA-2022-7c4aec44c8 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7c4aec44c8

Comment 4 Fedora Update System 2022-06-25 00:34:18 UTC
FEDORA-2022-7c4aec44c8 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-7c4aec44c8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7c4aec44c8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-07-05 16:37:58 UTC
FEDORA-2022-7c4aec44c8 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.