FS#72832 - [crystal] Package misses linker dependency

Attached to Project: Community Packages
Opened by Johannes Müller (straight-shoota) - Wednesday, 24 November 2021, 20:25 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After installing the crystal package on a fresh system, you can't really use the language because linking a program fails:

$ pacman -S crystal
$ crystal eval 'puts "Hello World"!
--: line 1: cc: command not found
Error: execution of command failed with code: 127: `cc "${@}" -o /root/.cache/crystal/crystal-run-eval.tmp -rdynamic -L/usr/bin/../lib/crystal -lpcre -lm -lgc -lpthread -levent -lrt -ldl`

Building a Crystal program requires a linker is available (`cc` or anything else configured via `CC` env var). Without a linker, the package is mostly unusable.

I think the package should depend on `gcc` or any other package that provides a suitable linker. Technically, you don't need `gcc` if you have say a different linker installed. Not sure if there are solutions for this in PKGBUILD (such as virtual packages). But a hard dependency on `gcc` is better than having no linker available.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:03 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/crystal/issues/1
Comment by Anatol Pomozov (anatolik) - Thursday, 02 December 2021, 19:24 GMT
Adding toolchain folks for their opinion.
Comment by Toolybird (Toolybird) - Monday, 15 May 2023, 07:47 GMT
Yeah, it definitely needs `cc' of some kind. I'd vote for a simple dep on gcc. Done.

Loading...