GDC release 0.22

[Nick Sabalausky]

"Anders F Björklund" <afb at algonet.se> wrote in message 
news:eslrbm$15q8$1 at digitalmars.com...
> Nick Sabalausky wrote:
>
>>>gdcwin: MinGW32 i386, MinGW GCC 3.4.5 ("Candidate" 20060117-1)
>>>        from gdc-0.22-mingw32-gcc-3.4.5.tar.bz2
>>
>> Pardon if this is a stupid question, but I'm unclear on one thing 
>> regarding trying to compile GDC from sources: Can GDC be built on 
>> MSYS/MinGW using GCC 3.4.2, or will it fail unless I upgrade GCC to 
>> 3.4.5?
>
> For my part I just got bored with building two sets of my packages when
> there are now official tarballs from the actual GDC development project.
>
> It used to build OK with MinGW GCC 3.4.2 when I did the GDC 0.21 builds,
> but I haven't tried since. The post D 1.0 packages now all use David's.
>
>> The reason I ask is that I'm currently getting build errors, and this 
>> snippit looks like it *might* be saying I need to go up to 3.4.5+, but 
>> I'm not sure.
>
> As far as I know, all versions of GCC 3.4.x are supported by GDC.
> Maybe your build errors are about something else ? (any details ?)
>
> I used this: http://gdcwin.sourceforge.net/gcc-3.4.2-build.sh
> after unpacking GCC and GDC and running the setup-gcc.sh script.
>
> --anders

I got errors at different places depending on whether or not I include c++.

With c++, it errored around libcpp "0 [main] make 2264 open_stackdumpfile: 
Dumping stack trace to make.exe.stackdump". I think I did something sightly 
different that time than in subsequent runs though. I may want to retry 
this.

If I omit c++, then it fails while compiling phobos 
(std/c/windows/com.d:240: error: '*LTHUNK0' aliased to undefined symbol 
'_D3std1c7windows3com9ComObject14QueryInterfaceMWPS3std1c7windows3com4GUIDPPvZi')

If I omit gdc, and build just c, or just c and c++, then it compiles fine.

That was all with a plain "make" with no paramaters and most, but not all, 
of the configure paramaters you used in that build script you just posted. 
I'm trying c/c++/d with all the configure and make paramaters you used right 
now. We'll see what happens.

A few things I should note:

1. I'm not sure which version of GCC you were patching GDC against, but I'm 
building
 against version 4.1.2. To clarify all the versionings: I'm using MSYS/MinGW 
GCC 3.5.2
 to build GDC 0.22 (old now, I know) against the GCC 4.1.2 sources.

This did originally create one problem: I would always get the following 
error no matter what languages (c++,d) were included or excluded:

Makefile:1280: *** target pattern contains no '%'. Stop.

After googling, I found that after running configure, I needed to go into 
the makefile and change the line:

LD = D:{a big giant mess here}ld.exe

To:

LD = ld

Which solved that problem. (I have no idea why it was happening, but it 
seems to be a common problem when trying to build GCC 4.x.x on MSYS/MinGW)


2. Not sure if it matters, but configure scripts tell me that someting about 
symbolic links isn't working. It reports "ln" works, but "ln -s" doesn't. 
Not sure if that matters. I have only a passing familiarity with symlinks


3. Also not sure if it matters, but at times I've noticed the compiler 
spitting out the following (I know warnings are normal while building gcc, 
but these are regarding commandline paramaters rather than the source being 
compiled):

cc1plus.exe: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
cc1plus.exe: warning: command line option "-Wmissing-prototypes" is valid 
for Ada/C/ObjC but not for C++