| 1 |
On Tuesday 06 May 2008, Ned Ludd wrote: |
| 2 |
> On Tue, 2008-05-06 at 17:24 -0400, Mike Frysinger wrote: |
| 3 |
> > On Tuesday 06 May 2008, Christopher Friedt wrote: |
| 4 |
> > > This is a 'chicken / egg' problem. In order to build a cross compiler |
| 5 |
> > > for arch X you need mpfr compiled for arch X. In order to build mpfr |
| 6 |
> > > for arch X you need a toolchain for arch X. |
| 7 |
> > > |
| 8 |
> > > Try building the cross-compiler without mpfr first, then build libmpfr, |
| 9 |
> > > and then rebuild the cross compiler. |
| 10 |
> > |
| 11 |
> > you cant build gcc-4.3 without gmp and mpfr. they're hard requirements. |
| 12 |
> > but they're requirements that the host system has it, not that they are |
| 13 |
> > cross-compiled for the target. |
| 14 |
> |
| 15 |
> this might pose a problem at Gentoo as I don't think mpfr can even be |
| 16 |
> cross compiled in the first place. I might be wrong but I seem to recall |
| 17 |
> fighting with it in the last week using ( arm-softfloat-linux-uclibc || |
| 18 |
> arm*-softloat-linux-gnueabi). |
| 19 |
|
| 20 |
i said they are host libraries, not target libraries. gcc itself uses them in |
| 21 |
order to even execute in the first place starting with gcc-4.3. |
| 22 |
|
| 23 |
what Christopher is probably referring to is gfortran support ... it requires |
| 24 |
mpfr/gmp to be cross-compiled. |
| 25 |
|
| 26 |
but to address your question, they both do cross-compile fine. i just did it |
| 27 |
two days ago for mingw32 target so that i could build up a gfortran |
| 28 |
cross-compiler. |
| 29 |
-mike |
Archives