From patchwork Sat Feb 4 18:16:09 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Jonathan Wakely X-Patchwork-Id: 139587 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id B2A5B104799 for ; Sun, 5 Feb 2012 05:16:32 +1100 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1328984193; h=Comment: DomainKey-Signature:Received:Received:Received:Received: MIME-Version:Received:Received:In-Reply-To:References:Date: Message-ID:Subject:From:To:Cc:Content-Type:Mailing-List: Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:Sender:Delivered-To; bh=dIxel6y8PlOA21CQ19xRpKO1imU=; b=Wz7fodTNNUwCRFn/8Q20ia9ZsiVBOXERpLTp93WErhG10VHoBgVI6HHBc56xx/ S9c1g3HjS3cLisN3F82Hk7zB7VYZyT1UTETSzWoOoYEvk9/LZJaHFnWvCq7Jcwne rK2DqCoMqtMLIXhrn0IKAVO6luEukC/9I2d8ofu7PBQhQ= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=IyGqK1hCBcnhGadG8aHAGGXnHNs66nl/IkLTU52rrQUJDAS71oJgdar0JoLBFz RyAKmVGyKhMdSwwtHftbTVcP7TClZckh+ZPGNfymwYvsT8nd9nOgrRXLsXkKe+Ek RXYlaa1raleLB9SJ7xm7SJ4+KNJH8oGLFPlz95YMJEv5E=; Received: (qmail 7754 invoked by alias); 4 Feb 2012 18:16:28 -0000 Received: (qmail 7745 invoked by uid 22791); 4 Feb 2012 18:16:27 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL, BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-lpp01m010-f47.google.com (HELO mail-lpp01m010-f47.google.com) (209.85.215.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 04 Feb 2012 18:16:11 +0000 Received: by lahc1 with SMTP id c1so2463649lah.20 for ; Sat, 04 Feb 2012 10:16:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.128.163 with SMTP id np3mr6146669lab.51.1328379369112; Sat, 04 Feb 2012 10:16:09 -0800 (PST) Received: by 10.112.39.42 with HTTP; Sat, 4 Feb 2012 10:16:09 -0800 (PST) In-Reply-To: References: Date: Sat, 4 Feb 2012 18:16:09 +0000 Message-ID: Subject: Re: adjust installation docs to discourage installing GMP, MPFR and MPC separately From: Jonathan Wakely To: Richard Guenther Cc: Quentin Neill , gcc-patches Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org On 31 January 2012 15:13, Jonathan Wakely wrote: >> Can we at least recommend using the OS vendors versions of the >> libraries in case they match our minimum (not recommended) version >> requirements?  Is our in-tree build support robust enough against >> newer/older OS vendor installed copies? > > Arguably the minimum versions are recommended by "Newer versions may > work in some cases, but it's safer to use the exact versions > documented." > > I will revise the patch to suggest vendor-supplied versions first, > then in-tree, then finally using --with-gmp (which is the method that > causes the most frequently asked questions) The attached patch suggests using vendor packages as the simplest way to install the support libs. OK for trunk? * doc/install.texi (Prerequisites): Suggest building GMP, MPFR and MPC as part of GCC before describing configuring with --with-gmp etc. (Installing GCC: Configuration): State that --with-gmp etc. aren't needed if sources are present. diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index da84758..2dcaef7 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -328,37 +328,42 @@ others optional. While any sufficiently new version of required tools usually work, library requirements are generally stricter. Newer versions may work in some cases, but it's safer to use the exact versions documented. We appreciate bug reports about problems with -newer versions, though. +newer versions, though. If your OS vendor provides packages for the +support libraries then using those packages may be the simplest way to +install the libraries. @table @asis @item GNU Multiple Precision Library (GMP) version 4.3.2 (or later) -Necessary to build GCC@. If you do not have it installed in your +Necessary to build GCC@. If a GMP source distribution is found in a +subdirectory of your GCC sources named @file{gmp}, it will be built +together with GCC, this avoids the need to build GMP separately. +Alternatively, if GMP is already installed but it is not in your library search path, you will have to configure with the @option{--with-gmp} configure option. See also @option{--with-gmp-lib} -and @option{--with-gmp-include}. Alternatively, if a GMP source -distribution is found in a subdirectory of your GCC sources named -@file{gmp}, it will be built together with GCC@. +and @option{--with-gmp-include}. @item MPFR Library version 2.4.2 (or later) Necessary to build GCC@. It can be downloaded from -@uref{http://www.mpfr.org/}. The @option{--with-mpfr} configure -option should be used if your MPFR Library is not installed in your -default library search path. See also @option{--with-mpfr-lib} and -@option{--with-mpfr-include}. Alternatively, if a MPFR source -distribution is found in a subdirectory of your GCC sources named -@file{mpfr}, it will be built together with GCC@. +@uref{http://www.mpfr.org/}. If an MPFR source distribution is found +in a subdirectory of your GCC sources named @file{mpfr}, it will be +built together with GCC, this avoids the need to build MPFR separately. +Alternatively, if MPFR is already installed but it is not in your +default library search path, the @option{--with-mpfr} configure +option should be used. See also @option{--with-mpfr-lib} and +@option{--with-mpfr-include}. @item MPC Library version 0.8.1 (or later) Necessary to build GCC@. It can be downloaded from -@uref{http://www.multiprecision.org/}. The @option{--with-mpc} -configure option should be used if your MPC Library is not installed -in your default library search path. See also @option{--with-mpc-lib} -and @option{--with-mpc-include}. Alternatively, if an MPC source -distribution is found in a subdirectory of your GCC sources named -@file{mpc}, it will be built together with GCC@. +@uref{http://www.multiprecision.org/}. If an MPC source distribution +is found in a subdirectory of your GCC sources named @file{mpc}, it +will be built together with GCC, this avoids the need to build MPC +separately. Alternatively, if MPC is already installed but it is +not in your default library search path, the @option{--with-mpc} +configure option should be used. See also @option{--with-mpc-lib} +and @option{--with-mpc-include}. @item Parma Polyhedra Library (PPL) version 0.11 @@ -1608,9 +1613,10 @@ When neither of these configure options are used, the default will be @itemx --with-mpc=@var{pathname} @itemx --with-mpc-include=@var{pathname} @itemx --with-mpc-lib=@var{pathname} -If you do not have GMP (the GNU Multiple Precision library), the MPFR -library and/or the MPC library installed in a standard location and -you want to build GCC, you can explicitly specify the directory where +If you want to build GCC but do not have GMP (the GNU Multiple Precision +library), the MPFR library and/or the MPC library installed in a +standard location and don't have their sources present in the GCC +source tree then you can explicitly specify the directory where they are installed (@samp{--with-gmp=@var{gmpinstalldir}}, @samp{--with-mpfr=@/@var{mpfrinstalldir}}, @samp{--with-mpc=@/@var{mpcinstalldir}}). The