On 20 March 2012 19:48, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:

> On 3/20/12, Andrew Wiley <wiley.andrew.j@gmail.com> wrote:
> > I'm not really sure why Daniel isn't just zipping the full install so you don't have to download TDM GCC separately. Might be some licensing issue there or something.
>
> I think it's fine the way it is. When GDC gets merged with the GCC mainline we will probably see GDC being distributed in the TDM setup. Otherwise why bloat the GDC zip with binaries you might not even need. Remember that the TDM setup can install c, c++, fortran, objc, openmp. Plus, you might already have TDM installed.
>

It's just a couple of DLL's, it'll barely change the size of the GDC
distribution.
I think you don't understand the average windows user. It need to just
work, you shouldn't need to jump through hoops to use the binary
distribution.

First, I want apologize.  For the lack of a responses lately and because I didn't include installation instructions in the latest release notices, but they are still included in the readme that comes in every release.

Second, I'd like to offer some background on why I chose the method of distribution I did.

For a long time, GDC2 on Windows didn't work.  That combined with the constant work being done on GDC, I wanted to package only the minimal number of files necessary.  Since I'm using exactly the same arguments(scripts really) as was used to compile TDM, it made it simple enough to drop in the GDC bits.

That allowed the rapid updating to newer versions of GDC by extracting into TDM-GCC again.  Very useful when needing to test in an unpolluted environment.

Starting with the first working release that supported TLS back in January, things got complicated.  Currently, there is a patch for GCC, binutils, and the MinGW runtime required to support TLS.  The GCC patch makes TLS incompatible between D and any other language.  The binutils only adds new functionality and fixes a bug.  The MinGW runtime files can really break things, because I also had to update to a newer version.  This was something I did note in the last release.

I have submitted the binutils and runtime patches but haven't heard much.  The GCC patch needs cleaning up before I'm willing to submit it.

I also deliberately wanted the install to be done with a zip file to keep away the faint of heart.  GDC/MinGW contained many bugs and I wanted it to be known it wasn't ready for use.  Additionally, it also allows rapid updating to more recent builds.  Now that GDC is current with DMD the need for rapid releases has disappeared and it may be possible to release quasi-stable binaries.

I'm going to update GDC/MinGW to tip and release a new zip file.  If there are no serious issues and Iain agrees, I'll consider doing a beta release and making an installer.  Mostly it depends on if I feel that the release can be usable long term.  I really have no interest in maintaining a fourth MinGW installer(mingw, mingw-w64, TDM).

Best Regards,

Daniel Green

On 25 March 2012 01:34, Daniel Green <venix1@gmail.com> wrote:

> First, I want apologize.  For the lack of a responses lately and because I didn't include installation instructions in the latest release notices, but they are still included in the readme that comes in every release.
>
> Second, I'd like to offer some background on why I chose the method of distribution I did.
>
> For a long time, GDC2 on Windows didn't work.  That combined with the constant work being done on GDC, I wanted to package only the minimal number of files necessary.  Since I'm using exactly the same arguments(scripts really) as was used to compile TDM, it made it simple enough to drop in the GDC bits.
>
> That allowed the rapid updating to newer versions of GDC by extracting into TDM-GCC again.  Very useful when needing to test in an unpolluted environment.
>
> Starting with the first working release that supported TLS back in January, things got complicated.  Currently, there is a patch for GCC, binutils, and the MinGW runtime required to support TLS.  The GCC patch makes TLS incompatible between D and any other language.  The binutils only adds new functionality and fixes a bug.  The MinGW runtime files can really break things, because I also had to update to a newer version.  This was something I did note in the last release.
>
> I have submitted the binutils and runtime patches but haven't heard much.
>  The GCC patch needs cleaning up before I'm willing to submit it.
>
> I also deliberately wanted the install to be done with a zip file to keep away the faint of heart.  GDC/MinGW contained many bugs and I wanted it to be known it wasn't ready for use.  Additionally, it also allows rapid updating to more recent builds.  Now that GDC is current with DMD the need for rapid releases has disappeared and it may be possible to release quasi-stable binaries.
>
> I'm going to update GDC/MinGW to tip and release a new zip file.  If there are no serious issues and Iain agrees, I'll consider doing a beta release and making an installer.  Mostly it depends on if I feel that the release can be usable long term.  I really have no interest in maintaining a fourth MinGW installer(mingw, mingw-w64, TDM).
>
> Best Regards,
>
> Daniel Green
>

Cheers for the info. Here's hoping the release works out well.
What instabilities are you primarily concerned about with the existing
release? I've been using it for a couple of weeks, and had no problems. Are
there particular things you anticipate causing issues?

On 3/24/2012 8:35 PM, Manu wrote:
> Cheers for the info. Here's hoping the release works out well.
> What instabilities are you primarily concerned about with the existing
> release? I've been using it for a couple of weeks, and had no problems.
> Are there particular things you anticipate causing issues?

The current release gave undefined thunks when heavily mixing classes and interfaces from different modules.  My pet project wouldn't link  I haven't had the time to dig into it and it may not be MinGW specific.

It generates errors like https://bitbucket.org/goshawk/gdc/issue/284/ but is not using LTO.

Additionally, I'd like to have a better testing procedure for such releases and find a reliable way to use gdmd outside of MSYS.

On 25 March 2012 05:55, Daniel Green <venix1@gmail.com> wrote:

> On 3/24/2012 8:35 PM, Manu wrote:
> > Cheers for the info. Here's hoping the release works out well.
> > What instabilities are you primarily concerned about with the existing
> > release? I've been using it for a couple of weeks, and had no problems.
> > Are there particular things you anticipate causing issues?
>
> The current release gave undefined thunks when heavily mixing classes and interfaces from different modules.  My pet project wouldn't link  I haven't had the time to dig into it and it may not be MinGW specific.
>
> It generates errors like https://bitbucket.org/goshawk/**gdc/issue/284/<https://bitbucket.org/goshawk/gdc/issue/284/>but is not using LTO.
>
> Additionally, I'd like to have a better testing procedure for such releases and find a reliable way to use gdmd outside of MSYS.
>

Are there work arounds if I should happen to run in to this? GDC is currently the only win64 compiler. I'm putting a lot of faith it in for the time being.

On 3/25/2012 5:10 AM, Manu wrote:
> Are there work arounds if I should happen to run in to this? GDC is
> currently the only win64 compiler. I'm putting a lot of faith it in for
> the time being.

Until it's found why it happens, I can't say how to avoid it.  Roughly I think it may be related to the following scenario spread among multiple source files but I haven't been able to reproduce it yet.

interface IA {}
interface IB {}

class CA : IA {}

class CB : CA, IB {}

More has to happen like having methods defined as well.


It's important to me to have a working MinGW64 GDC compiler as well.  I just have to finish converting the testsuite to DejaGNU and it'll be the next thing I do.

I'm trying to test gdc for Win/x64, I too get the same errors about missing dll's.

This was my process:

1. Install tdm64-gcc-4.7.1-3.exe
2. Extract gcc-4.6.1-tdm64-1-gdc-20121117-D2.060.7z to the MinGW64 install dir.

Tried running gdc.exe and x86_64-w64-mingw32-gdc.exe and both complain about missing dlls. The dlls files exist

\MinGW64\libexec\gcc\x86_64-w64-mingw32\4.7.1\

(gdc is in the MinGW64\bin dir)

Copying the dlls to the gdc allows it to find them(So obviously there is a path issue. Someone is making an assuming where the libs should be found but hasn't told the rest of us).

The new error is

/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.6.1/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lgcc

I've tried copying the root bin to this bin's dir but no luck.

Also, when I run gdc under visual D I get the original missing dll's errors.

So there seems to be a huge issue with how mingw-gdc is using paths. (Does a LIB environmental variable need to be set?)

As far as the last error, I'm not sure. I've never really used gcc and there is virtually no info on that error on google. I can compile the d code but cannot link it.

On 11/27/2012 6:37 AM, js.mdnq wrote:
> I'm trying to test gdc for Win/x64, I too get the same errors about
> missing dll's.
>
> This was my process:
>
> 1. Install tdm64-gcc-4.7.1-3.exe
> 2. Extract gcc-4.6.1-tdm64-1-gdc-20121117-D2.060.7z to the MinGW64
> install dir.

You will need to use the gcc-4.6.1 version of TDM.  You can find the installer at http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/Previous/1.1006.0/

The missing DLL error is probably a result of different versions being used for the support libs.  The same error occurs when using TDM32 binaries with TDM64 DLL.  Even though both releases use 32-bit binaries.

On Wednesday, 28 November 2012 at 07:29:53 UTC, Daniel Green wrote:
> On 11/27/2012 6:37 AM, js.mdnq wrote:
>> I'm trying to test gdc for Win/x64, I too get the same errors about
>> missing dll's.
>>
>> This was my process:
>>
>> 1. Install tdm64-gcc-4.7.1-3.exe
>> 2. Extract gcc-4.6.1-tdm64-1-gdc-20121117-D2.060.7z to the MinGW64
>> install dir.
>
> You will need to use the gcc-4.6.1 version of TDM.  You can find the installer at http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/Previous/1.1006.0/
>
> The missing DLL error is probably a result of different versions being used for the support libs.  The same error occurs when using TDM32 binaries with TDM64 DLL.  Even though both releases use 32-bit binaries.

Thanks, that's it. I would also like to point out that one should disable the automatic updates in the TDM installer as it will update to the latest version.

So now:

1. Install tdm64-gcc-4.6.1.exe
1. install gcc-4.6.1-tdm64-1-gdc-20121117-D2.060.7z

gdc works without any of the errors.

I'll assume that for future reference the gdc's gcc version must always must the tdm's version to avoid these types of issues. Please correct me I'm wrong.

On 11/28/2012 6:59 AM, js.mdnq wrote:
> I'll assume that for future reference the gdc's gcc version must always
> must the tdm's version to avoid these types of issues. Please correct me
> I'm wrong.

That's correct.  At some point, it's possible I may release GDC standalone from TDM.  When that happens it'll have it's own installer.