From patchwork Fri Dec 30 13:29:23 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Jonathan Wakely X-Patchwork-Id: 133643 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 B6B73B6F62 for ; Sat, 31 Dec 2011 00:29:45 +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=1325856587; h=Comment: DomainKey-Signature:Received:Received:Received:Received: MIME-Version:Received:Received:In-Reply-To:References:Date: Message-ID:Subject:From:To:Content-Type:Mailing-List:Precedence: List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender: Delivered-To; bh=uDbYlfnr+EpWlXZvhNbNEPxS878=; b=MHaVo+oi1D90usc lORM+z5D0wQBkfEqdA3kSY6f5Ul+t3c1sERNR8/1jsH44YEVZC92Krr22xABibtf K0cMIRtWblubwn0vkTw/5/wzSs6Y0vhygcqArh0NF7MTMGWaGxs/yXNnyORXmJZZ VDNbvqENiFATqf/Zk8z/iw8IxUG0= 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:Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=GSkor9+8Di05hH5rJeiWiVLBrNH0KXdYmi1AL/h81Gic2eqpk6Y5MeJ/JPlkSo 72/0gOVo+6+bcStF2CCPTK60ysvlaMpe44f+HLvX1m6fJSEErMtd80eFBpsguKTn PQWMMhuQGIiha0nNYwfhq+LyRvsOKRYNbAQHTmmpEyw10=; Received: (qmail 32452 invoked by alias); 30 Dec 2011 13:29:42 -0000 Received: (qmail 32443 invoked by uid 22791); 30 Dec 2011 13:29:40 -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-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 30 Dec 2011 13:29:25 +0000 Received: by wibhq7 with SMTP id hq7so7999991wib.20 for ; Fri, 30 Dec 2011 05:29:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.90.40 with SMTP id bt8mr86808425wib.4.1325251763403; Fri, 30 Dec 2011 05:29:23 -0800 (PST) Received: by 10.216.28.194 with HTTP; Fri, 30 Dec 2011 05:29:23 -0800 (PST) In-Reply-To: References: Date: Fri, 30 Dec 2011 13:29:23 +0000 Message-ID: Subject: Re: adjust installation docs to discourage installing GMP, MPFR and MPC separately From: Jonathan Wakely To: 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 22 December 2011 00:23, Jonathan Wakely wrote: > The most frequently asked question on gcc-help, and a frequently > reported "bug" in bugzilla, is > http://gcc.gnu.org/wiki/FAQ#configure_suffix > > It is almost always caused by installing libgmp.so etc. in a > non-standard location and not using ldconfig, DT_RUNPATH, > $LD_LIBRARY_PATH or some other method to tell the dynamic linker how > to find them.  The current installation docs mention --with-gmp right > away, which probably gives the impression that it's the recommended > method, whereas it actually causes problems for the majority of users > who don't understand dynamic linker search paths.  I think rewording > the installation docs to suggest building the support libs as part of > GCC first, and only using --with-gmp second, might steer people in the > right direction. > > Separately, I also plan to write an "Installing GCC" page on the GCC > wiki which (among other things) discourages installing the support > libraries by hand, recommending installing prebuilt packages in > standard system dirs instead, or if that's not an option then using > contrib/download_prerequisites to get the sources and build them > in-tree. > > >        * doc/install.text (Prerequisites): Suggest building GMP, MPFR and >        MPC as part of GCC before describing configuring with --with-gmp etc. > > Tested by running "make doc" and viewing the resulting .info pages, OK > for trunk? Here's an updated patch which also adjusts the --with-gmp docs in the Configuration chapter to mention the option of putting the support lib sources under the GCC sources * 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. OK for trunk? Index: doc/install.texi =================================================================== --- doc/install.texi (revision 182629) +++ doc/install.texi (working copy) @@ -333,32 +333,35 @@ newer versions, though. @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 +1611,10 @@ When neither of these configure options @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