[PATCH]: GMP/MPFR in-tree build instructions [Was: Re: [PATCH]: bump minimum MPFR version, (includes some fortranbits)]

[Tobias Schlüter]

Matt Fago wrote:
> I and several other people have been bit by this, and I am currently trying to 
> help someone else build gcc with gmp/mpfr. It seems to me that the easiest thing 
> to do is an in-tree build -- it would be great if it were documented. How about 
> something like the below? While generalizing the binutils paragraph would be 
> more concise, building gmp/mpfr is now often required and I though giving it a 
> separate paragraph was more clear.
> 
> Note I don't have write access, but I'd hope someone could commit something similar.

I'll take care of this, provided Gerald approves the change.  Gerald, if 
you think that copyright is a problem, I'll gladly rephrase it.

Thanks,
- Tobi

> *** download.html       2008-10-14 10:24:31.000000000 -0600
> --- download-new.html   2008-10-14 10:29:49.000000000 -0600
> *************** components of the binutils you intend to
> *** 107,112 ****
> --- 107,118 ----
>   (<samp><span class="file">bfd</span></samp>, <samp><span 
> class="file">binutils</span></samp>, <samp><span class="file">gas</span></samp>, 
> <samp><span class="file">gprof</span></samp>, <samp><span 
> class="file">ld</span></samp>,
>   <samp><span class="file">opcodes</span></samp>, <small 
> class="dots">...</small>) to the directory containing the GCC sources.
> 
> +    <p>A similar method can also be used to automatically build gmp and/or mpfr
> + 'in-tree.' Unpack the gmp and mpfr source distributions in the gcc source
> + directory and rename them to <samp><span class="file">gmp</span></samp> and
> + <samp><span class="file">mpfr</span></samp> (or use symbolic links with
> + the same name).
> +
>      <p><hr />
>   <p><a href="./index.html">Return to the GCC Installation page</a>