David Nadlinger:

> I would very much appreciate any help on crushing the remaining bugs (it's not rocket science), see http://wiki.dlang.org/Building_LDC_on_MinGW_x86 for build instructions.

Why don't you create one zip or rar, that a user unpacks, adds a path, and tries the compiler?

Bye,
bearophile

On Thursday, 14 February 2013 at 23:19:38 UTC, bearophile wrote:
> David Nadlinger:
>
>> I would very much appreciate any help on crushing the remaining bugs (it's not rocket science), see http://wiki.dlang.org/Building_LDC_on_MinGW_x86 for build instructions.
>
> Why don't you create one zip or rar, that a user unpacks, adds a path, and tries the compiler?

Because it's not ready for general consumption yet. For binary packages for the other platforms, see the last release announcement: http://forum.dlang.org/thread/yxklohfbaltbcdnkpnqw@forum.dlang.org.

David

On 2/14/13, David Nadlinger <see@klickverbot.at> wrote:
> I would very much appreciate any help on crushing the remaining bugs (it's not rocket science), see http://wiki.dlang.org/Building_LDC_on_MinGW_x86 for build instructions.

I suppose I'll give this a try tonight. However these steps should really be part of a nice and simple D script that does this automatically. Only then can we be sure the instructions are up to date, + it will save time for potential contributors.

If I get a working build done I'll try writing such a script. I'm eager to escape the wrath of Optlink on win32. :p

David Nadlinger:

> Because it's not ready for general consumption yet.

If trying the compiler is so complex/hard/time consuming as it looks, I will probably not try it. And maybe other people will do the same. So it will take even more time to find its bugs.

Bye,
bearophile

On Friday, 15 February 2013 at 00:02:00 UTC, bearophile wrote:
> David Nadlinger:
>
>> Because it's not ready for general consumption yet.
>
> If trying the compiler is so complex/hard/time consuming as it looks, I will probably not try it. And maybe other people will do the same. So it will take even more time to find its bugs.

If you don't want to contribute to LDC development, you shouldn't try it on MinGW yet. Simple as that.

When the test suite has turned green or near-green, we will of course release binary packages.

David

> http://wiki.dlang.org/Building_LDC_on_MinGW_x86 for build instructions.

It seems there is a bug in the MinGW TLS support patch linked from that page. This line:

+        DAG.getExternalSymbol("_tls_array"), getPointerTy());

should be

+        DAG.getExternalSymbol("_tls_array", getPointerTy()));

On Friday, 15 February 2013 at 02:41:47 UTC, jerro wrote:
>> http://wiki.dlang.org/Building_LDC_on_MinGW_x86 for build instructions.
>
> It seems there is a bug in the MinGW TLS support patch linked from that page. This line:
>
> +        DAG.getExternalSymbol("_tls_array"), getPointerTy());
>
> should be
>
> +        DAG.getExternalSymbol("_tls_array", getPointerTy()));

Yes, always those last-minute refactorings…

I fixed the Gist an hour or so ago.

David