Shame, OpenBSD is not supported
vm# curl -sSL https://get.wasp-lang.dev/installer.sh | sh
Sorry, this installer does not support your operating system: OpenBSD.
Possible to add OpenBSD support?
I use last release 7.3, node is v18.15.0
I can help on debugging.
13 Replies
Wohooo @Wesley974, you just became a Waspeteer level 1!
I just Opened an issue: https://github.com/wasp-lang/wasp/issues/1206
GitHub
Add OpenBSD Support · Issue #1206 · wasp-lang/wasp
Shame, OpenBSD is not supported. I use last release: 7.3 Node is v18.15.0 When I try: curl -sSL https://get.wasp-lang.dev/installer.sh | sh I get: Sorry, this installer does not support your operat...
Thanks @Wesley974 !
I have to admit I am not sure what is needed to do to support OpenBSD. Our installer script is not very long, I am guessing it wouldn't need to many chnages. If you want to give it a try, you could create a PR that makes it work.
Here is the script: https://github.com/wasp-lang/get-wasp/blob/master/installer.sh .
Another question would be if Wasp binary that we build for Linux would work on OpenBSD. Right now we build it on Ubuntu and that works quite well on most Linux distributions, but I am guessing OpenBSD would be too different?
Your best bet would probably be to try and compile/build Wasp localy on your machine, but again since we never tested on OpenBSD, I imagine there could be problems.
I would need the source to build the binary. Linux is very different.
OpenBSD is widely known for being the most secure operating system (created by the OpenBSD team) that developed OpenSSH. Porting this to OpenBSD would be very cool!
Here is the source with instructinos for building, in case you want to play with that: https://github.com/wasp-lang/wasp/tree/main/waspc .
Unfortunately if it turns out that there are significant changes needed to support OpenBSD, we probably won't have the resources at the moment to dedicate to that.
Ok, I will try first the shell script, then if necessary move on the src.
If it is too complex perhaps I could get it work, otherwise :/ 🙂
You should probably skip the shell script -> even if you get it working, there is no prebuilt binary for openBSD, closes is for Linux and I doubt that will work. So I would go for src immediately.
I tried the Darwin and Linux binaries, but they didn't work. Now I'm going to compile it from source. Below are the results:
vm# pwd
/var/www/htdocs/wasp/waspc
vm# cabal build
Error: cabal: Cannot find the program 'ghc'. User-specified path 'ghc-8.10.7'
does not refer to an executable and the program is not on the system path.
vm# whereis ghc
/usr/local/bin/ghc
vm# ghc
ghc: no input files
Usage: For basic information, try the
--help' option.
vm# echo $PATH
/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin
vm# ghc -v
Glasgow Haskell Compiler, Version 9.2.7, stage 2 booted by GHC version 8.10.7.20230316
*** initializing unit database:
Using binary package database: /usr/local/lib/ghc/package.conf.d/package.cache
package flags []
loading package database /usr/local/lib/ghc/package.conf.d
wired-in package ghc-prim mapped to ghc-prim-0.8.0
wired-in package ghc-bignum mapped to ghc-bignum-1.2
wired-in package base mapped to base-4.16.4.0
wired-in package rts mapped to rts
wired-in package template-haskell mapped to template-haskell-2.18.0.0
wired-in package ghc mapped to ghc-9.2.7
!!! initializing unit database: finished in 39.06 milliseconds, allocated 5.762 megabytes
*** Deleting temp files:
Deleting:
*** Deleting temp dirs:
Deleting:
ghc: no input files
Usage: For basic information, try the --help' option.
I don't know how to debug this, but if you want me to try some commands here and there, no problem. 🙂Sounds like your installation of haskell toolchain (cabal, gch) did not work out as it should -> Did you use ghcup to set it up? If not, it is the recommended way and it usually works out of the box: https://www.haskell.org/ghcup/ .
GHCup
GHCup is the main installer for the general purpose language Haskell.
Hum 😞
Ah too bad! Sorry about that then, this goes beyond our resources at the moment then.
News:
vm# cabal configure --with-compiler=/usr/local/bin/ghc
vm# pwd
/var/www/htdocs/wasp/waspc
vm# cabal build
Resolving dependencies...
Error: cabal: Could not resolve dependencies:
[0] trying: waspc-0.10.6 (user goal)
[1] next goal: template-haskell (dependency of waspc)
[1] rejecting: template-haskell-2.18.0.0/installed-2.18.0.0 (conflict: waspc
=> template-haskell^>=2.16.0)
[1] skipping: template-haskell-2.19.0.0, template-haskell-2.18.0.0,
template-haskell-2.17.0.0 (has the same characteristics that caused the
previous version to fail: excluded by constraint '^>=2.16.0' from 'waspc')
[1] rejecting: template-haskell-2.16.0.0, template-haskell-2.15.0.0,
template-haskell-2.14.0.0, template-haskell-2.13.0.0,
template-haskell-2.12.0.0, template-haskell-2.11.1.0,
template-haskell-2.11.0.0, template-haskell-2.10.0.0,
template-haskell-2.9.0.0, template-haskell-2.8.0.0, template-haskell-2.7.0.0,
template-haskell-2.6.0.0, template-haskell-2.5.0.0, template-haskell-2.4.0.1,
template-haskell-2.4.0.0, template-haskell-2.3.0.1, template-haskell-2.3.0.0,
template-haskell-2.2.0.0 (constraint from non-upgradeable package requires
installed instance)
[1] fail (backjumping, conflict set: template-haskell, waspc)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: waspc, template-haskell
Any idea?
Interesting, so basically Wasp requires template-haskell to be of version 2.16.*, to avoid any breaking changes (keep in mind this is not semver, this is PvP -> similar like semver, but has 4 number, and first two consistute major version together). So, cabal looks for version of template haskell that wasp is happy with but that others are also happy with. However, it fails to find such version! it rejects versions 2.17 and above -> ok, that makes sense, it should. But then it also rejects 2.16.0.0, which wasp is happy with! And it doesn't specify the reason, that is what is very weird.
My advice:
1. Make sure you ran
cabal update.
2. Which version of cabal are you using, and which version of ghc? We use ghc version as specified here https://github.com/wasp-lang/wasp/blob/main/waspc/cabal.project#L1, so I would expect cabal to warn you about that, but in case it didn't and you used another version, it might be a cause of the issue.
3. If none of this helps, maybe it is best to ask on cabal's gh repo for explanation of this error message -> not only might they help, but they might improve the messaging in the future.