Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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 Andreas Radke (AndyRTR) - Thursday, 02 December 2021, 19:21 GMT
Opened by Johannes Müller (straight-shoota) - Wednesday, 24 November 2021, 20:25 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 02 December 2021, 19:21 GMT
|
DetailsAfter 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

Adding toolchain folks for their opinion.