www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - GDC release 0.22

reply David Friedman <dvdfrdmn users.ess-eff.net> writes:
http://sourceforge.net/project/showfiles.php?group_id=154306

Changes:
   * Added support for GCC 4.1.x
   * Support for GCC 3.3.x is deprecated
   * Updated to DMD 1.004
   * Fixed Bugzilla 836, 837, 838, 839, 841, 843, 844, 889, 896
   * Fixed problems with missing debug information
   * Added Rick Mann's -frameowrk patch for gdmd

SkyOS support will return in the next release.
Feb 05 2007
next sibling parent reply Gregor Richards <Richards codu.org> writes:
David Friedman wrote:
 http://sourceforge.net/project/showfiles.php?group_id=154306
 
 Changes:
   * Added support for GCC 4.1.x
   * Support for GCC 3.3.x is deprecated
   * Updated to DMD 1.004
   * Fixed Bugzilla 836, 837, 838, 839, 841, 843, 844, 889, 896
   * Fixed problems with missing debug information
   * Added Rick Mann's -frameowrk patch for gdmd
 
 SkyOS support will return in the next release.

4.1.x support! Hoorah! - Gregor Richards
Feb 05 2007
parent Neal Becker <ndbecker2 gmail.com> writes:
Gregor Richards wrote:

 David Friedman wrote:
 http://sourceforge.net/project/showfiles.php?group_id=154306
 
 Changes:
   * Added support for GCC 4.1.x
   * Support for GCC 3.3.x is deprecated
   * Updated to DMD 1.004
   * Fixed Bugzilla 836, 837, 838, 839, 841, 843, 844, 889, 896
   * Fixed problems with missing debug information
   * Added Rick Mann's -frameowrk patch for gdmd
 
 SkyOS support will return in the next release.

4.1.x support! Hoorah!

Yeah! Now all I need is x86_64.
Feb 06 2007
prev sibling parent reply =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:
David Friedman wrote:

 http://sourceforge.net/project/showfiles.php?group_id=154306
 
 Changes:
   * Added support for GCC 4.1.x
   * Support for GCC 3.3.x is deprecated
   * Updated to DMD 1.004
   * Fixed Bugzilla 836, 837, 838, 839, 841, 843, 844, 889, 896
   * Fixed problems with missing debug information
   * Added Rick Mann's -frameowrk patch for gdmd

Regarding the gdcmac/gdcwin/gdcgnu packages, they are now offering the *same* GDC binaries as David provides. D 1.0 was the end of the line for the deprecated builds, like GCC 3.4.2 for MinGW and GCC 3.3 for Mac OS X 10.3. Going forward, these are the supported targets for each: gdcmac: Mac OS X 10.4 Universal, Apple GCC 4.0 (Xcode 2.4) from gdc-0.22-macosx-universal-gcc-5363.tar.bz2 gdcwin: MinGW32 i386, MinGW GCC 3.4.5 ("Candidate" 20060117-1) from gdc-0.22-mingw32-gcc-3.4.5.tar.bz2 gdcgnu: GNU/Linux i686/powerpc, FSF GCC 4.1.1 (20060524) * from gdc-0.22-i686-linux-gcc-4.1.1.tar.bz2 / gdc-0.22-powerpc-linux-gcc-4.1.1.tar.bz2 That is, whatever targets that the "dgcc" project offers... --anders Note: Fedora calls its GCC targets "i386-redhat-linux" and "ppc-redhat-linux", while Ubuntu instead calls them "i486-linux-gnu" and "powerpc-linux-gnu". So installing the GDC files shouldn't replace any system GCC binaries. (GDC uses "i686-pc-linux-gnu/"powerpc-unknown-linux-gnu") The duplicated files are: libgcc.a, crt*.o and collect2
Feb 06 2007
parent reply "Nick Sabalausky" <a a.a> writes:
"Anders F Björklund" <afb algonet.se> wrote in message 
news:eqaqsm$fat$1 digitaldaemon.com...
 D 1.0 was the end of the line for the deprecated builds,
 like GCC 3.4.2 for MinGW and GCC 3.3 for Mac OS X 10.3.

 Going forward, these are the supported targets for each:

 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? 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. (And yes, I see this GDC 0.22 is outdated since 0.23 just came out: I'll grab that in a bit)
Mar 06 2007
parent reply =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:
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
Mar 06 2007
parent reply "Nick Sabalausky" <a a.a> writes:
"Anders F Björklund" <afb algonet.se> wrote in message 
news:eslrbm$15q8$1 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++
Mar 07 2007
parent reply =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:
Nick Sabalausky wrote:

 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.

I was using either MinGW GCC 3.4.2 or 3.4.5, depending on when in time. I haven't used MinGW GCC 3.5, and I haven't used GCC 4.1.2 (on Windows)
 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

Yeah, Windows have a few quirks with symbolic links. So does Mac OS X, but it seems even worse on Windows. Not sure if it is fatal, though ? --anders
Mar 07 2007
parent reply "Nick Sabalausky" <a a.a> writes:
"Anders F Björklund" <afb algonet.se> wrote in message 
news:esmq4u$2qsn$1 digitalmars.com...
 Nick Sabalausky wrote:

 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.

I was using either MinGW GCC 3.4.2 or 3.4.5, depending on when in time. I haven't used MinGW GCC 3.5, and I haven't used GCC 4.1.2 (on Windows)

Oops, I meant 3.4.2, not 3.5.2. Sorry if I sound like I'm going in circles, but there's still something about the versions I'm unclear on regarding your build process. Let me see if I can explain better... There's two different GCC's involved: A. The one that actually being invoked by the build process to build GCC. It's the one that's already installed and working on the system prior to attempting to build GDC. B. The GCC sources that we're applying the D patches to. The one that is actually getting built. For me: A = 3.4.2 B = 4.1.2 If I'm understanding you correctly, yours is: A = 3.4.2 or 3.4.5, depending on when in time B = 3.4.2 or 3.4.5, depending on when in time Is this correct?
Mar 07 2007
parent reply =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:
Nick Sabalausky wrote:

 If I'm understanding you correctly, yours is:
 A = 3.4.2 or 3.4.5, depending on when in time
 B = 3.4.2 or 3.4.5, depending on when in time
 
 Is this correct?

Pretty much, but you can safely assume that A has been equal to 3.4.5 for my build of GDC 0.21 and that I'm not planning on doing any more builds of 3.4.2 (the 3.4.5 is old enough...) Not sure what compiler David uses, but I think it is 3.4.5 ? I'm using GCC 4.1.1 on Linux, but plan on sticking with the system versions for MinGW and Xcode: 3.4.5-20060117-1 for MinGW and 5363 for Xcode, i.e. the same as David is using... In a similar fashion my GDB is 6.3-20051128-2 for MinGW and 563 for Xcode, while the GNU/Linux version is using GDB 6.5. (it's following the availability of the GDB and GDC patches) It's mentioned on the web pages, and there's source code too. --anders
Mar 07 2007
next sibling parent "Nick Sabalausky" <a a.a> writes:
"Anders F Björklund" <afb algonet.se> wrote in message 
news:esn484$9tp$2 digitalmars.com...
 Nick Sabalausky wrote:

 If I'm understanding you correctly, yours is:
 A = 3.4.2 or 3.4.5, depending on when in time
 B = 3.4.2 or 3.4.5, depending on when in time

 Is this correct?

Pretty much, but you can safely assume that A has been equal to 3.4.5 for my build of GDC 0.21 and that I'm not planning on doing any more builds of 3.4.2 (the 3.4.5 is old enough...) Not sure what compiler David uses, but I think it is 3.4.5 ? I'm using GCC 4.1.1 on Linux, but plan on sticking with the system versions for MinGW and Xcode: 3.4.5-20060117-1 for MinGW and 5363 for Xcode, i.e. the same as David is using... In a similar fashion my GDB is 6.3-20051128-2 for MinGW and 563 for Xcode, while the GNU/Linux version is using GDB 6.5. (it's following the availability of the GDB and GDC patches) It's mentioned on the web pages, and there's source code too. --anders

Ok, then I guess I'm in fairly new territory building a GCC 4.1.x-based GDC on MSYS/MinGW. The last build I attempted should be done by now, though I'm away from home so I can't check how that went ATM. Normally, I'd just grab the GCC 3.x.x-based GDC bins and be done with it. But there's a reason I'm trying to get a specifically 4.1.x-based GDC built: There's another offshoot of GCC, devkitARM (part of the devkitPro project), that I'm trying to get built off of GDC instead of GCC, so I can get D going on the GBA/NDS handhelds (There's another person doing this on Linux instead of MinGW, don't know if he's been around here). The newer devkitARMs are built off of GCC 4.1.1, so I need to get this all working for at least 4.1.1 if I want to get my changes into the devkitPro trunk. I had some build problems when I attempted devkitARM + GDC + GCC 4.1.x, so I'm making sure I can get a plain GDC built off of 4.1.x before I merge it with devkitARM.
Mar 07 2007
prev sibling parent "Nick Sabalausky" <a a.a> writes:
"Anders F Björklund" <afb algonet.se> wrote in message 
news:esn484$9tp$2 digitalmars.com...
 Nick Sabalausky wrote:

 If I'm understanding you correctly, yours is:
 A = 3.4.2 or 3.4.5, depending on when in time
 B = 3.4.2 or 3.4.5, depending on when in time

 Is this correct?

Pretty much, but you can safely assume that A has been equal to 3.4.5 for my build of GDC 0.21 and that I'm not planning on doing any more builds of 3.4.2 (the 3.4.5 is old enough...) Not sure what compiler David uses, but I think it is 3.4.5 ? I'm using GCC 4.1.1 on Linux, but plan on sticking with the system versions for MinGW and Xcode: 3.4.5-20060117-1 for MinGW and 5363 for Xcode, i.e. the same as David is using... In a similar fashion my GDB is 6.3-20051128-2 for MinGW and 563 for Xcode, while the GNU/Linux version is using GDB 6.5. (it's following the availability of the GDB and GDC patches) It's mentioned on the web pages, and there's source code too. --anders

Ok, then I guess I'm in fairly new territory building a GCC 4.1.x-based GDC on MSYS/MinGW. The last build I attempted should be done by now, though I'm away from home so I can't check how that went ATM. Normally, I'd just grab the GCC 3.x.x-based GDC bins and be done with it. But there's a reason I'm trying to get a specifically 4.1.x-based GDC built: There's another offshoot of GCC, devkitARM (part of the devkitPro project), that I'm trying to get built off of GDC instead of GCC, so I can get D going on the GBA/NDS handhelds (There's another person doing this on Linux instead of MinGW, don't know if he's been around here). The newer devkitARMs are built off of GCC 4.1.1, so I need to get this all working for at least 4.1.1 if I want to get my changes into the devkitPro trunk. I had some build problems when I attempted devkitARM + GDC + GCC 4.1.x, so I'm making sure I can get a plain GDC built off of 4.1.x before I merge it with devkitARM.
Mar 07 2007