From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20164 invoked by alias); 1 Mar 2006 16:52:28 -0000 Received: (qmail 6007 invoked by uid 22791); 1 Mar 2006 16:24:22 -0000 X-Spam-Check-By: sourceware.org Date: Wed, 01 Mar 2006 16:52:00 -0000 Message-Id: <200603011624.k21GOIcS031219@sethra.codesourcery.com> From: Mark Mitchell To: gcc@gcc.gnu.org, gcc-announce@gcc.gnu.org Subject: GCC 4.1.0 Released Reply-to: mark@codesourcery.com Mailing-List: contact gcc-announce-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-announce-owner@gcc.gnu.org X-SW-Source: 2006/txt/msg00000.txt.bz2 GCC 4.1.0 has been released. This release is a major release, containing substantial new functionality relative to previous releases. See: http://gcc.gnu.org/gcc-4.1/changes.html for a list of new features, improvements, and other changes. This release is available from the FTP servers listed here: http://www.gnu.org/order/ftp.html The release is in the gcc/gcc-4.1.0 subdirectory. There are two important caveats beyond those listed on the web page above: 1. GNU TAR 1.14 is required to unpack the source releases. Other versions of tar are likely to report errors or silently unpack the file incorrectly. 2. It was discovered after the final release had been made that there is an installation problem when building with Java enabled and when "--enable-version-specific-runtime-libs" is in use . In particular, header files for some of the Java APIs will be placed in "/include" (with no prefix), due to a defect in the Java Makefiles. There are three known work-arounds: a) Disable Java by using "--enable-languages" when configuring GCC. For example, to build just the C and C++ compilers, use "--enable-languages=c,c++". b) Do not use "--enable-version-specific-runtime-libs". c) Use "--with-gxx-include-dir=" to explicitly indicate where you would like the Java header files to be placed. For example, if you use "--prefix=/path/to/prefix" then using: --with-gxx-include-dir=/path/to/prefix/lib/gcc//4.1.0 will place the header files in the appropriate version-specific location. I expect this problem will be corrected in GCC 4.1.1. If you encounter any difficulties using GCC 4.1.0, please do not send them directly to me. Instead, please http://gcc.gnu.org/ for information about getting help and filing problem reports. We expect to release GCC 4.0.3 (an bug-fix release relative to GCC 4.0.2) in the near future. GCC 4.1.1 (a bug-fix release for GCC 4.1.0) will be released in approximately two months. As usual, a vast number of people contributed to this release -- far too many to thank by name! -- Mark Mitchell CodeSourcery mark@codesourcery.com (650) 331-3385 x713