diff options
| -rw-r--r-- | content/posts/openbsd-compiling-rakudo-star/index.org | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/content/posts/openbsd-compiling-rakudo-star/index.org b/content/posts/openbsd-compiling-rakudo-star/index.org index 6ab16b9..dd5133b 100644 --- a/content/posts/openbsd-compiling-rakudo-star/index.org +++ b/content/posts/openbsd-compiling-rakudo-star/index.org @@ -11,8 +11,8 @@ I really enjoy using [[https://raku.org/][raku]] to write small scripts for syst maintenance and text parsing. Its regex and grammar engine are next level. The problem with using it on OpenBSD is that the packaged version is a couple years out of date. The version in ports is from -2018, which contains a big regarding to nativecall on OpenBSD. Not -to mention it's missing a lot of performance gains and patches. +2018, which contains a bug regarding NativeCall on OpenBSD. Not to +mention it's missing a lot of performance gains and patches. Instead of just compiling everything from source and installing them myself as I did on my last system, I installed it using the [[https://github.com/rakudo/star][rakudo @@ -20,22 +20,21 @@ star]] distribution and its =rstar= command. Rakudo Star is raku plus some community modules and the =zef= package manager. It also comes with the =rstar= command, which helps you in the build process. -Unfortunately, the first thing I had to do was install =bash=. as that +Unfortunately, the first thing I had to do was install =bash=, as that is what the =rstar= command is written in. #+BEGIN_SRC shell doas pkg_add bash #+END_SRC - After installing =bash=, I came across a problem. Running =rstar fetch= fetches all of the materials required to compile and assemble the star distribution, and while all of the community modules were successfully retrieved using =git=, it failed to pull in all 3 major source components. =MoarVM=, =nqp=, and =rakudo=, are pulled in as -gzipped tarballs, each of them failing to download correctly, which I -suspect is down to an issue with the bash scripts. Tar also throws a -warning about one of its arguments, which I suspect has to do with the +gzipped tarballs, each of them failing to download correctly. I +suspect it's an issue with something in the bash scripts. Tar also +throws a warning about one of its arguments, which has to do with the script using a GNU tar specific command. #+BEGIN_SRC |