On Wed, Nov 3, 2010 at 12:33 PM, Kfir Lavi <lavi.kfir@gmail.com> wrote:


On Tue, Nov 2, 2010 at 2:49 PM, Manuel Lauss <manuel.lauss@googlemail.com> wrote:
On Sun, Oct 31, 2010 at 9:08 AM, Kfir Lavi <lavi.kfir@gmail.com> wrote:
> Hi,
> I have a cross compilation environment inside a chroot.
> I run:
> i686-unknown-linux-gnu-emerge dev-libs/ace
> ...
> checking for i686-unknown-linux-gnu-g++... i686-unknown-linux-gnu-g++
> checking for C++ compiler default output file name... configure:
> error: C++ compiler cannot create executables

Have a look at config.log.  It tells exactly what went wrong, including gcc
error output.

Manuel

It seems that one of the steps that I do, is deleting the tools. I need then to install again from package from the mother system (I'm running here as chroot, and its very good that I did so).
So I install gcc and binutils, then compile them again in the chroot environment.
Using i686-unknown-linux-gnu-emerge and everything happens again.
I didn't find the culprit yet.

Kfir
 
It seems that installing dev-libs/ace is causing the problem.
emerge dev-libs/ace [works]
i686-gentoo-linux-gnu-g++ [works]
i686-gentoo-linux-gnu-gcc [works]
gcc [works]
g++ [works]
i686-gentoo-linux-gnu-emerge  dev-libs/ace [DONT WORK]

Other packages emerging ok with i686-gentoo-linux-gnu-emerge.
Can someone give me a hint? or something to check?

Thanks,
Kfir