public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>,
	  Anthony Green <green@moxielogic.com>,
	 gcc@gcc.gnu.org
Subject: Re: Problems with in-tree host libraries (gmp, ppl, etc)
Date: Mon, 04 May 2009 22:45:00 -0000	[thread overview]
Message-ID: <49FF6E64.3000902@codesourcery.com> (raw)
In-Reply-To: <49FE968E.10603@gnu.org>

Paolo Bonzini wrote:
>>> 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.
> 
> No, it was not.  So you can drop in gmp/mpfr, or ppl/cloog, but not all
> four.

I would like to again suggest that we declare in-tree builds of this
stuff out of scope.  Build them up front, pass configure options to say
where they can be found, and declare victory.

As GCC depends on more external libraries, it gets harder and harder for
us to maintain this build system.  We all want to get the build system
to the point where we're doing "staged installs", instead of the current
mess -- but the more we put into the build system the more complex it
becomes.  I think we should leave the process of building and installing
components to packaging systems like RPM or .deb or Cygwin.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

  reply	other threads:[~2009-05-04 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-02 14:24 Anthony Green
2009-05-03  7:01 ` Kaveh R. GHAZI
2009-05-04  7:17   ` Paolo Bonzini
2009-05-04 22:45     ` Mark Mitchell [this message]
2009-05-05  6:20       ` Paolo Bonzini
2009-05-06  8:11   ` Roberto Bagnara
2009-05-06 10:50     ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49FF6E64.3000902@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    --cc=green@moxielogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).