https://bugzilla.redhat.com/show_bug.cgi?id=2281419 --- Comment #9 from Jens Petersen <petersen@xxxxxxxxxx> --- (In reply to Benson Muite from comment #8) > Comments: > b) There is a static library > usr/lib64/tarm64le/libkernel.a > > Is this needed? If so, how is it used? Could it be made a dynamically linked > library? I am not an authority but I see it also in Alpine. Debian puts kernel.o and main.o into chezscheme-dev FreeBSD ports includes libkernel.a. Tumbleweed chezscheme also includes it. I suppose I could ask upstream for advice. > c) An object file is also packaged > usr/lib64/tarm64le/main.o > Perhaps this should be removed. I am not so sure: it is quite common for compilers to include such runtime files. See gcc even for example. > d) Upstream seems to also bundle nanopass and stex. Should the spec file > indicate these are bundled? Good point I will add those, thanks -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2281419 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202281419%23c9 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
