RejectedSoftware Forums

Sign up

Pages: 1 2

Re: LDC

On 5/9/13 3:22 AM, Andrew Edwards wrote:

On 5/8/13 8:37 AM, Sönke Ludwig wrote:

On Wed, 08 May 2013 06:51:11 -0400, Andrew Edwards wrote:

I'm running Ubuntu 12.10 but I don't thing that should matter.

Turns out that I have tested only the combinations CentOS+LDC and
Ubuntu+DMD, but Ubuntu+LDC needed the equivalent build fix as
Ubuntu+DMD (putting phobos before libcurl on the linker command line).
The current HEAD now also builds Ubuntu+LDC successfully (tested on
12.04, but 12.10 shouldn't make a difference in this case).

Progress! :)

 andrew@goldeneye:~/dub$ ./build.sh
 Running ldmd2...
 DUB has been built as bin/dub.

 You may want to run
 sudo ln -s /home/andrew/dub/bin/dub /usr/local/bin
 now.

But still not there yet:

 andrew@goldeneye:~/dub$ cd ../dtutor
 andrew@goldeneye:~/dtutor$ dub
 Illegal instruction (core dumped)

To complicate things a bit am not on Ubuntu 13.04. Trying everything I
can to make this work. Thanks for your assistance.

should be: I am now using Ubuntu 13.04.

Regards,
Andrew

Re: LDC

On Thu, 09 May 2013 03:28:33 -0400, Andrew Edwards wrote:

But still not there yet:

 andrew@goldeneye:~/dub$ cd ../dtutor
 andrew@goldeneye:~/dtutor$ dub
 Illegal instruction (core dumped)

Ugh, SIGILL often indicates that something wrong happens with LLVM code gen. My guess is that you may want to show the core dump to David (LDC author). While root issue may be in dub, getting to it from SIGILL is not that simple.

Re: LDC

Am 09.05.2013 09:28, schrieb Andrew Edwards:

But still not there yet:

 andrew@goldeneye:~/dub$ cd ../dtutor
 andrew@goldeneye:~/dtutor$ dub
 Illegal instruction (core dumped)

To complicate things a bit am not on Ubuntu 13.04. Trying everything I
can to make this work. Thanks for your assistance.

should be: I am now using Ubuntu 13.04.

I can't reproduce that. I've just installed a fresh Ubuntu 13.04 VM
(amd64) and built LDC using these instructions:
http://wiki.dlang.org/Building_LDC_from_source

Then ./build.sh ran without errors and I could also successfully create
and run a test project using

$ dub init test
$ cd test
$ dub --compiler=ldc2

Does maybe "dub --vv" print something useful?

Re: LDC

On 5/10/13 9:13 AM, Sönke Ludwig wrote:

Am 09.05.2013 09:28, schrieb Andrew Edwards:

But still not there yet:

  andrew@goldeneye:~/dub$ cd ../dtutor
  andrew@goldeneye:~/dtutor$ dub
  Illegal instruction (core dumped)

To complicate things a bit am not on Ubuntu 13.04. Trying everything I
can to make this work. Thanks for your assistance.

should be: I am now using Ubuntu 13.04.

I can't reproduce that. I've just installed a fresh Ubuntu 13.04 VM
(amd64) and built LDC using these instructions:
http://wiki.dlang.org/Building_LDC_from_source

Then ./build.sh ran without errors and I could also successfully create
and run a test project using

$ dub init test
$ cd test
$ dub --compiler=ldc2

Does maybe "dub --vv" print something useful?

Got frustrated with myself. Took a couple days off before returning to
give another try. Since the only thing I had installed on this machine
is Ubuntu, DMD, LDC, Vibe and the required libraries/programs to compile
them... I decide to start anew. So far so good. I've completed
installation of LDC and Vibe and everything seems to work thus far. Will
let you know if I have any more issues.

Thanks for the assistance,
Andrew

Re: LDC

That it somewhat disappointing :) SIGILL never should happen even in most weird environment so the fact popped once indicates that some bug is still hidden out there. But glad you have it working now!

Re: LDC

On Mon, 13 May 2013 07:32:02 GMT, Dicebot wrote:

That it somewhat disappointing :) SIGILL never should happen even in most weird environment so the fact popped once indicates that some bug is still hidden out there. But glad you have it working now!

Just found this old thread when searching for LDC+vibe.d bug reports, and thought I'd provide context on this: LLVM emits an illegal instruction (ud2) in several situations where a piece of code is not supposed to be reached, either for logically unreachable code, undefined behavior, or when directly calling the @llvm.trap intrinsic (as we do now e.g. for failed assertions in release mode, similar to DMD emitting a hlt).

David

Pages: 1 2