Hi Marc,

No improvement.
What I did:

echo $PATH
/usr/local/bin:/sw/bin:/sw/sbin:/opt/local/bin:/opt/local/sbin:/usr/ bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/ bin:/usr/X11R6/bin
noname:OSELAS.Toolchain markus$ which gcc
/usr/local/bin/gcc
noname:OSELAS.Toolchain markus$ more /usr/local/bin/gcc
#!/bin/bash
declare -a GCC_ARRAY
GCC_ARRAY=( $(type -a -P gcc) )
GCC="${GCC_ARRAY[1]}"

exec "${GCC}" -m32 "$...@}"


within my ptxdist directory:
make clean
configure
make
sudo make install


Within the OSELAS.Toolchain, which I didn't change.

ptxdist select ptxconfigs/powerpc-603e-linux- gnu_gcc-4.3.2_glibc-2.8_binutils-2.18_kernel-2.6.27-sanitized.ptxconfig
ptxdist go

Still this error:
configure: error: libgmp not found or uses a different ABI.

But actually I can try to build it on a 10.6 machine.
I will keep you updated,

Markus


Hello,

Markus Heidt wrote:
host-mpfr.get

checking for __gmpz_init in -lgmp... no
configure: error: libgmp not found or uses a different ABI.
Please read the INSTALL file -- see "In case of problem".
make: ***
[/Volumes/Development/cross/OSELAS.Toolchain/platform-powerpc-603e- linux-gnu-gcc-4.3.2-glibc-2.8-binutils-2.18-kernel-2.6.27-sanitized/ state/host-mpfr.prepare]

The (not so funny) thing is, that it worked on 10.6. The problem
probably is that gmp has been produced in 64 bit whereas mpfr wants to
link in 32 bits....or the other way round.

A real gross hack would be to create a script with the contents:

#!/bin/bash
declare -a GCC_ARRAY
GCC_ARRAY=( $(type -a -P gcc) )
GCC="${GCC_ARRAY[1]}"

exec "${GCC}" -m32 "$...@}"

and copy it to e.g.: "/usr/local/bin" and put "/usr/local/bin: in PATH
before /usr/bin (or whereever gcc lives).

you may have to rebuils the whole toolchain.

cheers, marc
--
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

--
ptxdist mailing list
[email protected]


--
ptxdist mailing list
[email protected]

Reply via email to