-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
7.0.1 tarball FTB on Debian buster #1767
Comments
Hey @JiffB, Try adding the Also, you could try building with https://github.com/PostgREST/postgrest/blob/main/.cirrus.yml#L31-L40 |
arm64 should work, I've managed to build it on ubuntu(with |
I add the -v switch, found one odd warning by around the middle of the compilation log:
which is strange, as I compile as root.
cabal is unknown, either in the FS or into /root/.stack:
From where I look from, this doesn't look nice :/ |
Check these, they might help:
The TMPDIR part seems relevant. |
Did not help - AFAII, the 2nd one implies that cabal is installed, but it isn't at this time. |
Besides compiling from source, have you tried the latest https://github.com/PostgREST/postgrest/releases/tag/nightly It's likely that it works on debian. |
I'm about to test the stable binary, but those only cover the amd64 architecture, when pREST has binaries for almost all… |
Closing as outdated. Related: #2273 |
Hi Haskell gurus,
Environment
Description of issue
I followed: https://postgrest.org/en/v7.0.0/development.html
so, once the haskell-stack package was installed, I issued:
waited for a long moment, time for ghc to install and launch compilation, but after some logs, I'm stuck on this:
This triggered 2 thoughts:
1)- OMFG, Haskell is even a better tease than Erlang when it comes to error messages,
2)- I'm doomed as I have tests to conduct under x86_64, arm64 and armhf :/)
Re-launching the compilation with: stack build --copy-bins --local-bin-path /usr/local/bin
also failed, which looks normal:
How can I succeed compiling postgrest as I really need it's features (especially pictures direct transfer to nginx as advertised in the docs) for a composite application ?
The text was updated successfully, but these errors were encountered: