www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Vibe-D Installation on Ubuntu x86 20.04

reply Selim Ozel <sozel wpi.edu> writes:
Hello Everyone,

I am having trouble deploying vibe-d on my Ubuntu instance on 
AWS. I tried following additional Linux instructions in [1] with 
no luck.

My hello world project which I create with "dub init <name> -t 
vibe.d" gets stuck in the command line with the following 
message: eventcore 0.9.10: building configuration "epoll"...

Then it just gets stuck.

Has anyone recently experienced this? I was planning to ask on 
rejected software forums but they still seem to be down.

Best,
S

[1] https://code.dlang.org/packages/vibe-d
Nov 18 2020
parent reply Petar Kirov [ZombineDev] <petar.p.kirov gmail.com> writes:
On Wednesday, 18 November 2020 at 22:19:08 UTC, Selim Ozel wrote:

 Hello Everyone,

 I am having trouble deploying vibe-d on my Ubuntu instance on 
 AWS. I tried following additional Linux instructions in [1] 
 with no luck.

 My hello world project which I create with "dub init <name> -t 
 vibe.d" gets stuck in the command line with the following 
 message: eventcore 0.9.10: building configuration "epoll"...

 Then it just gets stuck.

 Has anyone recently experienced this? I was planning to ask on 
 rejected software forums but they still seem to be down.

 Best,
 S

 [1] https://code.dlang.org/packages/vibe-d


Are you building locally, or on Amazon (say EC2 instance)? Also, 
are you mentioned "x86" in the title, but you are on a 64-bit OS, 
right?
Have you checked the memory usage during this build step? It's 
likely the machine you're building on doesn't have sufficient RAM 
and maybe swapping (which could cause compiling to be orders of 
magnitude slower.
Nov 18 2020
parent reply Selim Ozel <sozel wpi.edu> writes:
On Wednesday, 18 November 2020 at 22:25:50 UTC, Petar Kirov 
[ZombineDev] wrote:

 On Wednesday, 18 November 2020 at 22:19:08 UTC, Selim Ozel 
 wrote:

 [...]


 Are you building locally, or on Amazon (say EC2 instance)? 
 Also, are you mentioned "x86" in the title, but you are on a 
 64-bit OS, right?
 Have you checked the memory usage during this build step? It's 
 likely the machine you're building on doesn't have sufficient 
 RAM and maybe swapping (which could cause compiling to be 
 orders of magnitude slower.


I am building on EC2! I'll check the RAM usage etc ... tomorrow. 
That might be it. Thanks.

S
Nov 18 2020
parent reply Selim Ozel <sozel wpi.edu> writes:
On Wednesday, 18 November 2020 at 23:13:39 UTC, Selim Ozel wrote:

 On Wednesday, 18 November 2020 at 22:25:50 UTC, Petar Kirov 
 [ZombineDev] wrote:

 On Wednesday, 18 November 2020 at 22:19:08 UTC, Selim Ozel 
 wrote:

 [...]


 Are you building locally, or on Amazon (say EC2 instance)? 
 Also, are you mentioned "x86" in the title, but you are on a 
 64-bit OS, right?
 Have you checked the memory usage during this build step? It's 
 likely the machine you're building on doesn't have sufficient 
 RAM and maybe swapping (which could cause compiling to be 
 orders of magnitude slower.


 I am building on EC2! I'll check the RAM usage etc ... 
 tomorrow. That might be it. Thanks.

 S


Ramping up the memory limit of the instance to 8 gig solved it 
for me. Thanks so much for this tip.

Best,
S
Nov 19 2020
parent reply Selim Ozel <sozel wpi.edu> writes:
On Thursday, 19 November 2020 at 18:40:38 UTC, Selim Ozel wrote:

 On Wednesday, 18 November 2020 at 23:13:39 UTC, Selim Ozel 
 wrote:

 On Wednesday, 18 November 2020 at 22:25:50 UTC, Petar Kirov 
 [ZombineDev] wrote:

 On Wednesday, 18 November 2020 at 22:19:08 UTC, Selim Ozel 
 wrote:

 [...]


 Are you building locally, or on Amazon (say EC2 instance)? 
 Also, are you mentioned "x86" in the title, but you are on a 
 64-bit OS, right?
 Have you checked the memory usage during this build step? 
 It's likely the machine you're building on doesn't have 
 sufficient RAM and maybe swapping (which could cause 
 compiling to be orders of magnitude slower.


 I am building on EC2! I'll check the RAM usage etc ... 
 tomorrow. That might be it. Thanks.

 S


 Ramping up the memory limit of the instance to 8 gig solved it 
 for me. Thanks so much for this tip.

 Best,
 S


I have a follow up on this and I didn't want to create another 
topic for it. The simple hello world app I build with vibe-d does 
not seem to work on the second compile+execution. It throws a 
failed to listen on port/address error on console. I think it is 
the same error as in [1]. Although the commit in [2] hasn't 
seemed to fixed it for me. I appreciate any pointers.

I was also thinking about writing a tutorial about deployment on 
EC2 Ubuntu 20.04. Does anyone think that would be helpful?

Best,
Selim

[1] 
https://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/3480/
[2] 
https://github.com/vibe-d/vibe.d/commit/2fb92b7baac15d70e719c697c19521ca99aac71c
Nov 21 2020
parent Daniel Kozak <kozzi11 gmail.com> writes:
On Sat, Nov 21, 2020 at 11:20 PM Selim Ozel via Digitalmars-d <
digitalmars-d puremagic.com> wrote:


 ...
 I have a follow up on this and I didn't want to create another
 topic for it. The simple hello world app I build with vibe-d does
 not seem to work on the second compile+execution. It throws a
 failed to listen on port/address error on console. I think it is
 the same error as in [1]. Although the commit in [2] hasn't
 seemed to fixed it for me. I appreciate any pointers.

 I was also thinking about writing a tutorial about deployment on
 EC2 Ubuntu 20.04. Does anyone think that would be helpful?

 Best,
 Selim

 [1]

 https://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/3480/
 [2]

 https://github.com/vibe-d/vibe.d/commit/2fb92b7baac15d70e719c697c19521ca99aac71c



This is a known issue,  you have to set VibeHighEventPriority version for
eg if you are using dub with json format add:

"versions": ["VibeHighEventPriority"]
Nov 21 2020