I am trying to build a small application (I am using DUB) and when I try to build, I get the following output:

> dub build
dub: /usr/lib64/libcurl.so.4: no version information available (required by dub)
vibe-d: ["vibe-d", "libevent", "openssl"]
vibe-d: ["vibe-d", "libevent", "openssl"]
libd: ["libd", "vibe-d", "libevent", "openssl"]
classify: ["classify", "vibe-d", "libevent", "openssl", "libd", "vibe-d", "libevent", "openssl"]
Building vibe-d configuration "libevent", build type debug.
Running dmd...
FAIL ../../../../../.dub/packages/vibe-d-master/.dub/build/libevent-debug-linux.posix-x86_64-dmd-7A48A3727C6BBE022213B1765700F4A5 vibe-d staticLibrary
Error executing command build: DMD compile run failed with exit code -9

Does anyone know what 'exit code -9' means, or where I could even go to find a listing of what the various exit codes for DMD mean.  I've searched around the WWW a bit and can't find any such list.

On Wednesday, 19 February 2014 at 22:07:55 UTC, Craig Dillabaugh wrote:
> I am trying to build a small application (I am using DUB) and when I try to build, I get the following output:
>
>> dub build
> dub: /usr/lib64/libcurl.so.4: no version information available (required by dub)
> vibe-d: ["vibe-d", "libevent", "openssl"]
> vibe-d: ["vibe-d", "libevent", "openssl"]
> libd: ["libd", "vibe-d", "libevent", "openssl"]
> classify: ["classify", "vibe-d", "libevent", "openssl", "libd", "vibe-d", "libevent", "openssl"]
> Building vibe-d configuration "libevent", build type debug.
> Running dmd...
> FAIL ../../../../../.dub/packages/vibe-d-master/.dub/build/libevent-debug-linux.posix-x86_64-dmd-7A48A3727C6BBE022213B1765700F4A5 vibe-d staticLibrary
> Error executing command build: DMD compile run failed with exit code -9
>
> Does anyone know what 'exit code -9' means, or where I could even go to find a listing of what the various exit codes for DMD mean.
>  I've searched around the WWW a bit and can't find any such list.

I just realized that I tried to build this on my Linode, where DMD tends to choke and die with anything Vibe-d related (basic Linodes have very little RAM).  To many terminals open!  Same code/build config work fine at my workstation.

However, I would still be interested in finding out where I could get a listing of what the various exit codes mean ... or do I need to delve into the DMD source code?

On 2014-02-19 17:15, Craig Dillabaugh wrote:
> However, I would still be interested in finding out where I could get a
> listing of what the various exit codes mean ... or do I need to delve
> into the DMD source code?
>

That seems to be the SIGKILL signal from linux kernel (-9). DMD didn't have a chance to react when the OOME occured.

On Wednesday, 19 February 2014 at 22:15:47 UTC, Craig Dillabaugh wrote:
(...)
> I just realized that I tried to build this on my Linode, where DMD tends to choke and die with anything Vibe-d related (basic Linodes have very little RAM).  To many terminals open!  Same code/build config work fine at my workstation.
(...)

Just a little heads up in case you begin experiencing the same issues as me.
I've also choked my Linode and found out it's better to compile from my desktop.
One problem though is that I'm running x86_64 on my desktop and x86 on my Linode.
The compiled x86 program crashes on my desktop, but runs fine in my Linode.
Took some time before I actually tried running the crashing program on Linode...

On Thursday, 20 February 2014 at 08:10:06 UTC, simendsjo wrote:
> On Wednesday, 19 February 2014 at 22:15:47 UTC, Craig Dillabaugh wrote:
> (...)
>> I just realized that I tried to build this on my Linode, where DMD tends to choke and die with anything Vibe-d related (basic Linodes have very little RAM).  To many terminals open!  Same code/build config work fine at my workstation.
> (...)
>
> Just a little heads up in case you begin experiencing the same issues as me.
> I've also choked my Linode and found out it's better to compile from my desktop.
> One problem though is that I'm running x86_64 on my desktop and x86 on my Linode.
> The compiled x86 program crashes on my desktop, but runs fine in my Linode.
> Took some time before I actually tried running the crashing program on Linode...

Thanks for the tip.  My Host OS and my Linode are identical OpenSuse 13.1 (x86_64) and I did as you did (compile on my PC & then copy the executable to the Linode).  So far, so good for me.

On Wednesday, 19 February 2014 at 23:45:12 UTC, Etienne Cimon
wrote:
> On 2014-02-19 17:15, Craig Dillabaugh wrote:
>> However, I would still be interested in finding out where I could get a
>> listing of what the various exit codes mean ... or do I need to delve
>> into the DMD source code?
>>
>
> That seems to be the SIGKILL signal from linux kernel (-9). DMD didn't have a chance to react when the OOME occured.

Thanks.