-
Notifications
You must be signed in to change notification settings - Fork 3
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
capnp build error #28
Comments
From @kentonv on February 11, 2018 6:18 It appears as if Sandstorm isn't installed inside the Vagrant image, which is weird. Maybe there's some more initialization that needs to be done by vagrant-spk? TBH I have never used vagrant-spk so I don't really know. Maybe @dwrensha (who created the Wordpress package) has an idea. |
From @dwrensha on February 11, 2018 14:3
EDIT: hm. Those sandstorm files really should be there. When I do |
From @dwrensha on February 11, 2018 14:31 When I try to build https://github.com/dwrensha/wordpress-sandstorm, it looks like I get farther than you did, but I still hit an error:
I conjecture that this has to do with the fact that the |
From @kentonv on February 11, 2018 21:33 Ugh, apparently shared folders don't implement writable mmap(). I'm surprised they can get away with that. I guess maybe the capnp C++ output plugin needs to go back to using write(). Sad. |
This is the PR they used to fix their Vagrant 1.9.6 downloading the sandstorm version of the box: github.com/sandstorm-io/vagrant-spk/pull/209 Got that from @ocdtrekkie . I did change previously to probably broken box version. |
From @JamborJan on March 6, 2018 19:38 Hi guys, I have updated my fork of wordpress for Sandstorm (see https://github.com/JamborJan/wordpress-sandstorm/commit/cb93151f8b0901b6db1eb85aec7dbc28e230a4ef). Now I'm running into a different error:
I was not able yet to dig a bit deeper into these error messages but will do so as soon as possible. I wanted to leave a note here just in case someone of you can easily help or solve this. PS: @xet7 as soon as we have figured out how we deal with the app key I will contribute to your repo. Until then I use my fork for testing reasons. Otherwise I would not be able to build packages and test them. Thanks |
From @ocdtrekkie on March 6, 2018 19:44 @JamborJan payments.capnp is a weird thing to show up here. I know that @kentonv just merged that back into Sandstorm proper, so it's possible something's missing there, and it's never been an issue with building before for that reason: sandstorm-io/sandstorm#3042 |
No problem, a moment ago I did fetch and merge changes from your repo to this repo, and also add some more modifications for php5 to php7. I will look at app key when bulding wp-sandstorm works, and there is something worth releasing. |
From @JamborJan on March 7, 2018 8:3 You also took my sandstorm-pkgdef.capnp. I can send you my private app key (over another secure channel) so that you are able tu build packages. If this is okay for you, I would be able to delete my fork and use yours instead. |
Yes it's OK. You can install desktop or mobile client of https://about.riot.im so we can enable end-to-end encryption, my Riot nickname is xet7wekan |
Hey @ocdtrekkie, did I get your comment right and the payments.capnp will be analysed or is there something I need to do because I did something wrong when I tried to build the Wordpress app? |
I am just suspecting it's a new problem cause by the fact that payments.capnp is new to the Sandstorm repo. Kenton should be around this weekend and can probably explain why it's showing up as an error. |
It looks like there's a bug in the makefile:
This line is missing an argument:
It fails on payments.capnp because that file contains absolute imports rather than relative, which is vestigial since it used to live in Blackrock rather than Sandstorm. I will change it to use relative imports in today's release, but it may also make sense to fix the Wordpress app's Makefile. |
With latest changes in git I have this progress, after installing vagrant:
Then inside VirtualBox VM window, where is username: vagrant password: vagrant
Then on Firefox ESR http://local.sandstorm.io:6080 |
Related sandstorm-io/sandstorm#3054 |
I guess it's about the new PHP7 version according to the error log. I tried to run and enter a grain to figure out what is wrong but I ran into another issue (see sandstorm-io/vagrant-spk#213). I've realised that there are some php config files in the repo. There is one line which seems to be wrong for PHP7, but it seems these config files are not used at all. @xet7 I guess you added this symlink to solve the issue, which didn't work out. Right?
|
Yes, it did not work, it caused error about symlink to symlink, or something like that. |
I removed that symlink from repo. |
I am super excited that progress has been made here! |
From @xet7 on February 7, 2018 21:41
@kentonv
When I try to build wordpress-sandstorm .spk file in vagrant with this script:
https://github.com/wekan/wordpress-sandstorm/blob/master/build-spk-in-vagrant.sh
I get this error when building capnp. How can this be fixed?
BR,
xet7
Copied from original issue: wekan/wordpress-sandstorm#1
The text was updated successfully, but these errors were encountered: