GCC 4.0.0 build report on Fedora Core 3
GCC 4.0.0 has been successfully built on Fedora Core 3 Config.guess output: i686-pc-linux-gnu gcc -v output: Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.0.0/configure --prefix=/usr/local --mandir=/usr/local/share/man --infodir=/usr/local/share/info --enable-languages=ada,c,c++,f95,java --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions Thread model: posix gcc version 4.0.0 /etc/issue (first line): Fedora Core release 3 (Heidelberg) uname -a output: Linux gandalf 2.6.11-1.14_FC3 #1 Thu Apr 7 19:23:49 EDT 2005 i686 athlon i386 GNU/Linux glibc version as reported by rpm: glibc-2.3.5-0.fc3.1 The attempt to make HTML documentation crashes: make[1]: Entering directory `/home/jdg/gccbuild/i686-pc-linux-gnu/libada' make[1]: *** No rule to make target `html'. Stop. make[1]: Leaving directory `/home/jdg/gccbuild/i686-pc-linux-gnu/libada' make: *** [html-target-libada] Error 1 David Gressett Anatomical Medical Laboratories, Inc. Denton, TX
Failure building Ada on i686-pc-mingw32
Development environment: i686-pc-mingw32 on Windows 2000 Pro SP4 (Athlon processor) MinGW 3.2.0 (gcc 3.4.2 mingw-special) Msys 1.0.10 ../gcc-4.0.1/configure --verbose --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingwlocal --enable-threads --disable-nls --disable-win32-registry --disable-shared --enable-sjlj-exceptions --enable-languages=c,ada Ada fails in stage1; the offender is gnatbind.exe. It crashes even if invoked with no command-line arguments. Gdb provides the following information: (gdb) run Starting program: C:\gcc401install\gccbuild\gcc\stage1/gnatbind.exe Program received signal SIGSEGV, Segmentation fault. 0x004034b7 in __gnat_install_SEH_handler (ER=0x) at ../../gcc-4.0.1/gcc/ada/seh_init.c:219 219 ((int *)ER)[0] = (int)ptr; /* previous handler */ (gdb)
GNAT package GNAT.Traceback.Symbolic
What is the status of GNAT.Traceback.Symbolic? I have gcc 4.0.1 20050727 (Red Hat 4.0.1-5) on my Fedora C4 system, and gcc 3.4.2 (mingw-special) and gcc 3.4.5 on my Windows 2000 system. In all 3 of these, the source code comments in g-trasym.ads indicate that symbolic traceback doesn't work on all systems on which GNAT runs, but it does say that Linux and Windows are among the ones for which it does work. In fact it does not work; the offender is a missing libaddr2line. It does work with the GNAT GPL 2005 that I have on my XP box at home. A search of the gcc mailing list archive didn't turn up much, but there was one message which indicated that there was a license problem with the addr2line source code that the Ada Core people were using. If a working libaddr2line isn't going to show up anytime soon, the comments in g-trasym.ads should be modified appropriately.
Re: GCC 4.3 Platform List
Mark Mitchell wrote: Andrew Pinski wrote: On Wed, 2006-09-20 at 23:11 -0400, Mark Mitchell wrote: Reactions? Change powerpc-unknown-linux-gnu to powerpc64-unknown-linux-gnu so that we also require the 64bit of PowerPC to work. To be clear, you're suggesting that we say "powerpc64-unknown-linux-gnu", but mean that both it's 32-bit and 64-bit modes should work? That makes sense to me. What about MIPS/MIPS64? Also move powerpc64-unknown-linux-gnu or powerpc-linux-gnu to Primary if powerpc-aix is moving to secondary so we keep a PowerPC up as a primary target. Definitely; I'd confused myself. 5. Add i686-mingw32 as a secondary platform. Is i686-pc-cygwin just as important as mingw32 then? I wonder if you mean to ask whether mingw32 is as important as Cygwin, or the other way around? I think both are important, and about equally so. Cygwin is widely used by people used to GNU software when running on Windows and has a very active community. Windows (without Cygwin) is of course a widely-used operating system, and my perception is that a reasonable number of people are using GCC to build non-Cygwin Windows applications. However, I have no hard data. $0.02 from a user - I routinely use the MinGW gcc stuff, mostly the Ada compiler, in a production environment where I work. I'd love to see i686-mingw32 get more attention.
Re: RFH: GPLv3
$.02 from a user who has been following the discussion: 1. Don't jack with the version numbers. This is confusing. 2. Turn off public access to the code while changing license text in the source. 3. Backports to current stuff should stay under current licence, i.e. a gcc 4.2.1 containing bits and pieces of 4.3 should stay under GPLv2 until 4.3 is released. If a 4.2.2 comes out after the release of 4.3, it should go to GPLv3. I.e, all open branches should change licenses at once. 4. gcc should put a short reference to the license in the version string. My MingGW version of gcc describes itself as "gcc version 3.4.5 (mingw special)" A future MinGW version should do something like "gcc version 4.3.0 (mingw special) GPLv3". Every vendor who distributes a tweaked gcc should be requested to to implement this ASAP. 5. It probably wouldn't hurt to have a command-line option to describe the license(s) in more detail. This would be especially useful when using compilers from vendors like AdaCore who have products like GNAT GPL which has a run-time library that is governed by GPL rather than LGPL. 6. gcc isn't the only software product that will be affected by confusion about the license. gcc should provide a small license-display library that users can use in their own products. This would be easy enough for any user to implement, but if it comes with gcc, it would be more likely to be widely used.
