I am currently using the following packages on arch linux (parabola [1] to be exact):

- DUB version 1.0.0

- LDC version 1.0.0

I create a project with the following command:

$ dub init -t vibe.d vibetest

Change directories:

$ cd vibetest/

And attempt to build and run the project:

$ dub run

However, I get the following output:

Performing "debug" build using ldc2 for x86_64.
vibe-d:utils 0.7.29: building configuration "library"...
vibe-d:data 0.7.29: building configuration "library"...
vibe-d:core 0.7.29: building configuration "libevent"...
vibe-d:http 0.7.29: building configuration "library"...
vibe-d:diet 0.7.29: building configuration "library"...
vibe-d:mail 0.7.29: building configuration "library"...
vibe-d:mongodb 0.7.29: building configuration "library"...
vibe-d:redis 0.7.29: building configuration "library"...
vibe-d:web 0.7.29: building configuration "library"...
vibe-d 0.7.29: building configuration "libevent"...
vibetest ~master: building configuration "application"...
Running ./vibetest
Fatal Error while loading '/usr/lib/libphobos2-ldc.so.70':
        The module 'std.base64' is already defined in './vibetest'.
Program exited with code 1

I don't even know where to start with this error. Normal projects without vibe.d compile and run perfectly well; replacing app.d contents with void main() {} still produces the same error.

[1] https://parabola.nu/

On Monday, 29 August 2016 at 20:32:27 UTC, e-y-e wrote:
> [...]

Does anyone know of anywhere else I can get help with this error? It's a blocker on me using vibe.d, which is quite frustrating.

Probably LDC issue https://github.com/ldc-developers/ldc/issues

On Thursday, 1 September 2016 at 09:37:22 UTC, Kagamin wrote:
> Probably LDC issue https://github.com/ldc-developers/ldc/issues

Thank you for your reply. I built LDC (version 1.1.0 beta 2) from source and ran dub using:

$ dub run --compiler="~/Downloads/ldc/bin/ldc2"

And everything works now, so it must have been. I looked through some of the issues and it surprises me that I was the only one having this problem, but it must have been fixed at some point.

Anyway, thanks for your time, I feel a bit silly now :)