From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19686 invoked by alias); 3 May 2009 07:01:23 -0000 Received: (qmail 19278 invoked by uid 22791); 3 May 2009 07:01:22 -0000 X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_40 X-Spam-Check-By: sourceware.org Received: from caip.rutgers.edu (HELO caip.rutgers.edu) (128.6.236.16) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 03 May 2009 07:01:18 +0000 Received: from caipclassic.rutgers.edu (caipclassic.rutgers.edu [128.6.237.54]) by caip.rutgers.edu (8.13.8/8.13.8) with ESMTP id n4371DBD001220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 May 2009 03:01:15 -0400 Date: Sun, 03 May 2009 07:01:00 -0000 From: "Kaveh R. GHAZI" To: Anthony Green cc: gcc@gcc.gnu.org Subject: Re: Problems with in-tree host libraries (gmp, ppl, etc) In-Reply-To: <1241274289.21584.6.camel@dev.moxielogic.com> Message-ID: References: <1241274289.21584.6.camel@dev.moxielogic.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-05/txt/msg00044.txt.bz2 On Sat, 2 May 2009, Anthony Green wrote: > The top level configury suggests that you can simply drop gmp, ppl, etc > into the top level source dir and they will get configured and used. > Does this really work? It is supposed to. I haven't worked on or tested the ppl machinery so I don't know what shape it is in. > Index: Makefile.def > =================================================================== > --- Makefile.def (revision 146995) > +++ Makefile.def (working copy) > @@ -60,7 +60,7 @@ > host_modules= { module= gawk; }; > host_modules= { module= gettext; }; > host_modules= { module= gmp; lib_path=.libs; bootstrap=true; > - extra_configure_flags='--disable-shared'; > + extra_configure_flags='--disable-shared --enable-cxx'; > no_install= true; > host="none-${host_vendor}-${host_os}"; > target="none-${host_vendor}-${host_os}"; }; I would only pass in this flag if ppl is being used. Look at what I did with extra_mpfr_configure_flags in the top level directory. You can use a similar mechanism to have a flag passed in to the gmp build conditionally. > Even then, the ppl configury isn't detecting the gmp we just built. It > seems as though we should install gmp in a local temporary install tree > and point ppl at that. See below for a trace of the ppl configury as it > attempts to detect an in-tree gmp (after applying the patch above). > AG I don't know if ppl was ever setup to detect/use an in-tree gmp. It would need to be able to specify --with-gmp-build= or something equivalent to get the header and library from a build tree rather than an install tree. They're laid out slightly differently. --Kaveh