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
