public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
To: Anthony Green <green@moxielogic.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Problems with in-tree host libraries (gmp, ppl, etc)
Date: Sun, 03 May 2009 07:01:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.58.0905030255300.2693@caipclassic.rutgers.edu> (raw)
In-Reply-To: <1241274289.21584.6.camel@dev.moxielogic.com>

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

  reply	other threads:[~2009-05-03  7:01 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 [this message]
2009-05-04  7:17   ` Paolo Bonzini
2009-05-04 22:45     ` Mark Mitchell
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=Pine.GSO.4.58.0905030255300.2693@caipclassic.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc@gcc.gnu.org \
    --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).