www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - Error on dub build - Trying Vibe-d for the first time

reply Bruno Rodrigues <bruno.sushirod gmail.com> writes:
So, I tried building a simple hello world with Vibe-d and got 
this error


 /usr/bin/ld: cannot find -lssl
 /usr/bin/ld: cannot find -lcrypto
 collect2: error: ld returned 1 exit status
 Error: linker exited with status 1
 /usr/bin/dmd failed with exit code 1.


I have absolutely no ideia what these libraries are.

I'm using linux 20.04

The project was created with dub the same way the dependency was 
added.

Thanks, this language seems to be really interesting.
Oct 13 2020
parent reply Steven Schveighoffer <schveiguy gmail.com> writes:
On 10/13/20 8:40 PM, Bruno Rodrigues wrote:

 So, I tried building a simple hello world with Vibe-d and got this error
 

 /usr/bin/ld: cannot find -lssl
 /usr/bin/ld: cannot find -lcrypto
 collect2: error: ld returned 1 exit status
 Error: linker exited with status 1
 /usr/bin/dmd failed with exit code 1.


 
 I have absolutely no ideia what these libraries are.
 
 I'm using linux 20.04
 
 The project was created with dub the same way the dependency was added.
 
 Thanks, this language seems to be really interesting.


sudo apt-get install libssl-dev

That should get you running.

-Steve
Oct 13 2020
parent reply Bruno Rodrigues <bruno.sushirod gmail.com> writes:
On Wednesday, 14 October 2020 at 01:32:34 UTC, Steven 
Schveighoffer wrote:

 On 10/13/20 8:40 PM, Bruno Rodrigues wrote:

 So, I tried building a simple hello world with Vibe-d and got 
 this error
 

 /usr/bin/ld: cannot find -lssl
 /usr/bin/ld: cannot find -lcrypto
 collect2: error: ld returned 1 exit status
 Error: linker exited with status 1
 /usr/bin/dmd failed with exit code 1.


 
 I have absolutely no ideia what these libraries are.
 
 I'm using linux 20.04
 
 The project was created with dub the same way the dependency 
 was added.
 
 Thanks, this language seems to be really interesting.


 sudo apt-get install libssl-dev

 That should get you running.

 -Steve


Thank you, Steve!

It did work but none of the examples on the Vibe.d page are 
working with current D version...


Some errors I got

When executing with dub


 [main(----) INF] Listening for requests on http://[::]:8080/
 Failed to listen on 0.0.0.0:8080
 Hello, World: /
 Warning (thread: main): leaking eventcore driver because there 
 are still active handles
   FD 6 (streamListen)
   FD 9 (streamSocket)

Warning (thread: main): leaking eventcore driver because there 
are still active handles
   FD 6 (streamListen)
   FD 9 (streamSocket)


When compiling (dub, dub build or dub build --force), I got a lot 
of deprecation errors


 /usr/include/dmd/phobos/std/format.d(3648,26): Deprecation: 
 function std.typecons.Nullable!(Alternate).Nullable.get_ is 
 deprecated - Implicit conversion with alias Nullable.get this 
 will be removed after 2.096. Please use .get explicitly.
Oct 14 2020
parent reply Andre Pany <andre s-e-a-p.de> writes:
On Wednesday, 14 October 2020 at 13:20:53 UTC, Bruno Rodrigues 
wrote:

 On Wednesday, 14 October 2020 at 01:32:34 UTC, Steven 
 Schveighoffer wrote:

 [...]


 Thank you, Steve!

 It did work but none of the examples on the Vibe.d page are 
 working with current D version...


 Some errors I got

 When executing with dub


   [...]


 When compiling (dub, dub build or dub build --force), I got a 
 lot of deprecation errors


 [...]




Please add this to your dub.json file:
"versions": [ "VibeHighEventPriority" ]

You may have to restart your pc 1 time. After that the issue 
should not occur anymore. (It is a known bug).

Kind regards
Andre
Oct 14 2020
next sibling parent reply Imperatorn <johan_forsberg_86 hotmail.com> writes:
On Wednesday, 14 October 2020 at 15:27:46 UTC, Andre Pany wrote:

 On Wednesday, 14 October 2020 at 13:20:53 UTC, Bruno Rodrigues 
 wrote:

 On Wednesday, 14 October 2020 at 01:32:34 UTC, Steven 
 Schveighoffer wrote:

 [...]


 Thank you, Steve!

 It did work but none of the examples on the Vibe.d page are 
 working with current D version...


 Some errors I got

 When executing with dub


   [...]


 When compiling (dub, dub build or dub build --force), I got a 
 lot of deprecation errors


 [...]




 Please add this to your dub.json file:
 "versions": [ "VibeHighEventPriority" ]

 You may have to restart your pc 1 time. After that the issue 
 should not occur anymore. (It is a known bug).

 Kind regards
 Andre


Where is this documented?
Oct 14 2020
parent reply Andre Pany <andre s-e-a-p.de> writes:
On Wednesday, 14 October 2020 at 16:39:39 UTC, Imperatorn wrote:

 On Wednesday, 14 October 2020 at 15:27:46 UTC, Andre Pany wrote:

 On Wednesday, 14 October 2020 at 13:20:53 UTC, Bruno Rodrigues 
 wrote:

 On Wednesday, 14 October 2020 at 01:32:34 UTC, Steven 
 Schveighoffer wrote:

 [...]


 Thank you, Steve!

 It did work but none of the examples on the Vibe.d page are 
 working with current D version...


 Some errors I got

 When executing with dub


   [...]


 When compiling (dub, dub build or dub build --force), I got a 
 lot of deprecation errors


 [...]




 Please add this to your dub.json file:
 "versions": [ "VibeHighEventPriority" ]

 You may have to restart your pc 1 time. After that the issue 
 should not occur anymore. (It is a known bug).

 Kind regards
 Andre


 Where is this documented?


I dont know whether it is documented somewhere. It was asked 
multiple times in the forum therefore I remembered.

Maybe it could be documented in the vibe.d github wiki or on the 
vibe.d website. But hopefully the bug is solved soon.

Kind regards
Andre
Oct 14 2020
parent reply "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Wed, Oct 14, 2020 at 05:30:37PM +0000, Andre Pany via Digitalmars-d-learn
wrote:

 On Wednesday, 14 October 2020 at 16:39:39 UTC, Imperatorn wrote:

 On Wednesday, 14 October 2020 at 15:27:46 UTC, Andre Pany wrote:




[...]

 Please add this to your dub.json file:
 "versions": [ "VibeHighEventPriority" ]
 
 You may have to restart your pc 1 time. After that the issue
 should not occur anymore. (It is a known bug).






[...]

 Where is this documented?


 
 I dont know whether it is documented somewhere. It was asked multiple
 times in the forum therefore I remembered.
 
 Maybe it could be documented in the vibe.d github wiki or on the
 vibe.d website. But hopefully the bug is solved soon.


[...]

Yeah, this is a problem.  Things like these need to be put in the docs
in an easy-to-find way. Like collected in a Troubleshooting page or
something.  If a bug isn't filed yet, I'd file a bug on vibe.d so that
this will get resolved instead of forgotten, and then it will bite the
next newcomer all over again.


T

-- 
Many open minds should be closed for repairs. -- K5 user
Oct 14 2020
parent reply Andre Pany <andre s-e-a-p.de> writes:
On Wednesday, 14 October 2020 at 18:08:40 UTC, H. S. Teoh wrote:

 On Wed, Oct 14, 2020 at 05:30:37PM +0000, Andre Pany via 
 Digitalmars-d-learn wrote:

 On Wednesday, 14 October 2020 at 16:39:39 UTC, Imperatorn 
 wrote:

 On Wednesday, 14 October 2020 at 15:27:46 UTC, Andre Pany 
 wrote:




 [...]

 [...]






 [...]

 Where is this documented?


 
 I dont know whether it is documented somewhere. It was asked 
 multiple times in the forum therefore I remembered.
 
 Maybe it could be documented in the vibe.d github wiki or on 
 the vibe.d website. But hopefully the bug is solved soon.


 [...]

 Yeah, this is a problem.  Things like these need to be put in 
 the docs in an easy-to-find way. Like collected in a 
 Troubleshooting page or something.  If a bug isn't filed yet, 
 I'd file a bug on vibe.d so that this will get resolved instead 
 of forgotten, and then it will bite the next newcomer all over 
 again.


 T


https://github.com/search?q=VibeHighEventPriority&type=issues

It seems with eventcore 0.9.9 there was some fix, but I do not 
know whether this solves the bug or s.th. related to the bug.

Kind regards
Andre
Oct 14 2020
parent reply Steven Schveighoffer <schveiguy gmail.com> writes:
On 10/14/20 2:25 PM, Andre Pany wrote:

 On Wednesday, 14 October 2020 at 18:08:40 UTC, H. S. Teoh wrote:

 On Wed, Oct 14, 2020 at 05:30:37PM +0000, Andre Pany via 
 Digitalmars-d-learn wrote:

 On Wednesday, 14 October 2020 at 16:39:39 UTC, Imperatorn wrote:

 On Wednesday, 14 October 2020 at 15:27:46 UTC, Andre Pany > wrote:




 [...]

 [...]






 [...]

 Where is this documented?


 I dont know whether it is documented somewhere. It was asked multiple 
 times in the forum therefore I remembered.

 Maybe it could be documented in the vibe.d github wiki or on the 
 vibe.d website. But hopefully the bug is solved soon.


 [...]

 Yeah, this is a problem.  Things like these need to be put in the docs 
 in an easy-to-find way. Like collected in a Troubleshooting page or 
 something.  If a bug isn't filed yet, I'd file a bug on vibe.d so that 
 this will get resolved instead of forgotten, and then it will bite the 
 next newcomer all over again.


 T


 
 https://github.com/search?q=VibeHighEventPriority&type=issues
 
 It seems with eventcore 0.9.9 there was some fix, but I do not know 
 whether this solves the bug or s.th. related to the bug.
 


Is this the commit you are talking about?

https://github.com/vibe-d/eventcore/pull/122

I haven't tested turning the version definition off. But it probably 
should be easy enough to do a vanilla vibe-d install and see if it works.

I hope this is the fix, because this bug has been a huge problem, 
especially for people trying vibe for the first time.

-Steve
Oct 15 2020
parent reply Andre Pany <andre s-e-a-p.de> writes:
On Thursday, 15 October 2020 at 13:17:57 UTC, Steven 
Schveighoffer wrote:

 On 10/14/20 2:25 PM, Andre Pany wrote:

 On Wednesday, 14 October 2020 at 18:08:40 UTC, H. S. Teoh 
 wrote:

 On Wed, Oct 14, 2020 at 05:30:37PM +0000, Andre Pany via 
 Digitalmars-d-learn wrote:

 [...]






 [...]

 [...]






 [...]

 [...]


 [...]

 Yeah, this is a problem.  Things like these need to be put in 
 the docs in an easy-to-find way. Like collected in a 
 Troubleshooting page or something.  If a bug isn't filed yet, 
 I'd file a bug on vibe.d so that this will get resolved 
 instead of forgotten, and then it will bite the next newcomer 
 all over again.


 T


 
 https://github.com/search?q=VibeHighEventPriority&type=issues
 
 It seems with eventcore 0.9.9 there was some fix, but I do not 
 know whether this solves the bug or s.th. related to the bug.
 


 Is this the commit you are talking about?

 https://github.com/vibe-d/eventcore/pull/122

 I haven't tested turning the version definition off. But it 
 probably should be easy enough to do a vanilla vibe-d install 
 and see if it works.

 I hope this is the fix, because this bug has been a huge 
 problem, especially for people trying vibe for the first time.

 -Steve


I meant this one:
https://github.com/vibe-d/eventcore/pull/154

I testing it at the moment, while there still "leaking" warnings, 
the ports are released after terminating the application with 
Ctrl+c. So far I was not able to reproduce the issue with vibe.d 
0.9.2 (eventcore 0.9.9).

Kind regards
Andre
Oct 15 2020
parent reply Steven Schveighoffer <schveiguy gmail.com> writes:
On 10/15/20 9:55 AM, Andre Pany wrote:


 
 I meant this one:
 https://github.com/vibe-d/eventcore/pull/154
 
 I testing it at the moment, while there still "leaking" warnings, the 
 ports are released after terminating the application with Ctrl+c. So far 
 I was not able to reproduce the issue with vibe.d 0.9.2 (eventcore 0.9.9).


Soo.... if you try to print a warning it keeps the process alive? I 
can't understand how this would fix it. It is still printing too, so how 
could that have fixed the problem?

-Steve
Oct 15 2020
parent reply Steven Schveighoffer <schveiguy gmail.com> writes:
On 10/15/20 10:22 AM, Steven Schveighoffer wrote:

 On 10/15/20 9:55 AM, Andre Pany wrote:
 

 I meant this one:
 https://github.com/vibe-d/eventcore/pull/154

 I testing it at the moment, while there still "leaking" warnings, the 
 ports are released after terminating the application with Ctrl+c. So 
 far I was not able to reproduce the issue with vibe.d 0.9.2 (eventcore 
 0.9.9).


 
 Soo.... if you try to print a warning it keeps the process alive? I 
 can't understand how this would fix it. It is still printing too, so how 
 could that have fixed the problem?
 


Not fixed. I just did the same test (dub init -t vibe.d) and it fails to 
kill the process. Still have to kill with -9.

-Steve
Oct 15 2020
parent Andre Pany <andre s-e-a-p.de> writes:
On Thursday, 15 October 2020 at 14:26:37 UTC, Steven 
Schveighoffer wrote:

 On 10/15/20 10:22 AM, Steven Schveighoffer wrote:

 On 10/15/20 9:55 AM, Andre Pany wrote:
 

 I meant this one:
 https://github.com/vibe-d/eventcore/pull/154

 I testing it at the moment, while there still "leaking" 
 warnings, the ports are released after terminating the 
 application with Ctrl+c. So far I was not able to reproduce 
 the issue with vibe.d 0.9.2 (eventcore 0.9.9).


 
 Soo.... if you try to print a warning it keeps the process 
 alive? I can't understand how this would fix it. It is still 
 printing too, so how could that have fixed the problem?
 


 Not fixed. I just did the same test (dub init -t vibe.d) and it 
 fails to kill the process. Still have to kill with -9.

 -Steve


You are right, I only tested it on Windows. Here it is working 
(stopping with ctrl+c and starting again) except the warnings.

Kind regards
Andre
Oct 15 2020
prev sibling parent reply Bruno Rodrigues <bruno.sushirod gmail.com> writes:
On Wednesday, 14 October 2020 at 15:27:46 UTC, Andre Pany wrote:

 On Wednesday, 14 October 2020 at 13:20:53 UTC, Bruno Rodrigues 
 wrote:

 On Wednesday, 14 October 2020 at 01:32:34 UTC, Steven 
 Schveighoffer wrote:

 [...]


 Thank you, Steve!

 It did work but none of the examples on the Vibe.d page are 
 working with current D version...


 Some errors I got

 When executing with dub


   [...]


 When compiling (dub, dub build or dub build --force), I got a 
 lot of deprecation errors


 [...]




 Please add this to your dub.json file:
 "versions": [ "VibeHighEventPriority" ]

 You may have to restart your pc 1 time. After that the issue 
 should not occur anymore. (It is a known bug).

 Kind regards
 Andre


Thanks, Andre! I'll try this solution later.
Oct 14 2020
parent Bruno Rodrigues <bruno.sushirod gmail.com> writes:
So, it did work...

The problem was on me, I guess.

I was using this example:

 https://tour.dlang.org/tour/en/dub/vibe-d


It wasn't working at all...


So I've changed to this one, and it did work.

 https://code.dlang.org/packages/vibe-d/0.9.2


I've used the first example, there are some differences to the 
one on tour.dlang.

Thanks all for the support.
Oct 14 2020