From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PDicX-00061t-ES for garchives@archives.gentoo.org; Wed, 03 Nov 2010 19:03:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9FE7BE07A0 for ; Wed, 3 Nov 2010 19:03:40 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 2D9B9E0746 for ; Wed, 3 Nov 2010 18:32:48 +0000 (UTC) Received: by wyb40 with SMTP id 40so1101657wyb.40 for ; Wed, 03 Nov 2010 11:32:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=gVsdjA1rGLmhmkEU+CeQ9qlN+8nTbzj8OrmFe+t7CHA=; b=IDP9sj3pZgugSOR7mr1FQL2q3mUqhQ1KCbBg0DV0bKlKP7YewG7t+cCZBFYy5rPjKv DoEqpA+7ZPYcJ3NW0RLspzyI8Earfr95O4M1vaVDt9ctQ07qZVyVfYTR6Y863ivtAiU6 VJ1uRfLNdniruBk0qt7CXolJTHNUISqJOInms= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=yGlEBSzDXXywQKzTFVW6uHPTeuArdTytLx6Yk7pyA0c7QkL8kFLqnBX4WKU3kftm31 TsDwnZsF+cP2lD01QqaDdE2IdB9bnFM6TNASh6a0g6iLhCDaStAV0O8fliI/A2jO5q6F 0q3Y2P4BsIUqlYYBgRvyDAu2UNV+6k+u7AgCw= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@lists.gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org MIME-Version: 1.0 Received: by 10.227.141.201 with SMTP id n9mr11274784wbu.185.1288809166779; Wed, 03 Nov 2010 11:32:46 -0700 (PDT) Received: by 10.216.133.96 with HTTP; Wed, 3 Nov 2010 11:32:46 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Nov 2010 20:32:46 +0200 Message-ID: Subject: Re: [gentoo-embedded] configure: error: C++ compiler cannot create executables From: Kfir Lavi To: gentoo-embedded@lists.gentoo.org Content-Type: multipart/alternative; boundary=001636831db291b64504942a44c2 X-Archives-Salt: f49c766a-6aa1-4f18-80c4-ee356359e378 X-Archives-Hash: 747de1b4c26748dc68af41f8f4afea1c --001636831db291b64504942a44c2 Content-Type: text/plain; charset=UTF-8 On Wed, Nov 3, 2010 at 7:50 PM, Kfir Lavi wrote: > > > On Wed, Nov 3, 2010 at 12:33 PM, Kfir Lavi wrote: > >> >> >> On Tue, Nov 2, 2010 at 2:49 PM, Manuel Lauss > > wrote: >> >>> On Sun, Oct 31, 2010 at 9:08 AM, Kfir Lavi 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 > Some diagnostics: $ cd /usr/__CHOST__/tmp/portage/dev-libs/ace-5.7.2/work/ACE_wrappers/build $ ../configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for egrep... grep -E checking whether #! works in shell scripts... yes checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E Here we see that configure passes the test it failed with emerge. One line did grab my attention: checking whether we are cross compiling... no Maybe the environment that i686-gentoo-linux-gnu-emerge creates is not working for ACE. What do you think? Regards, Kfir --001636831db291b64504942a44c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


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


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


On= Tue, Nov 2, 2010 at 2:49 PM, Manuel Lauss <manuel.lauss@googlem= ail.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++<= br> > checking for C++ compiler default output file name... configure:
> error: C++ compiler cannot create executables

Have a look at config.log. =C2=A0It tells exactly what went wrong, in= cluding 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 enviro= nment.
Using i686-unknown-linux-gnu-emerge and everything happens again.=
I didn't find the culprit yet.

Kfir
=C2=A0
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=C2=A0 dev-libs/ace [DONT WORK]

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

Thanks,
Kfir

Some diagnostics:
$ cd /usr/__CHOST__/tmp/portage= /dev-libs/ace-5.7.2/work/ACE_wrappers/build
$ ../configure
checking b= uild system type... i686-pc-linux-gnu
checking host system type... i686-= pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-comp= atible install... /usr/bin/install -c
checking whether build environment= is sane... yes
checking for gawk... gawk
checking whether make sets = $(MAKE)... yes
checking for egrep... grep -E
checking whether #! works in shell scripts= ... yes
checking for g++... g++
checking for C++ compiler default out= put file name... a.out
checking whether the C++ compiler works... yes checking whether we are cross compiling... no
checking for suffix of exe= cutables...
checking for suffix of object files... o
checking whethe= r we are using the GNU C++ compiler... yes
checking whether g++ accepts = -g... yes
checking for style of include used by make... GNU
checking dependency st= yle of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
Here we see that configure passes the test it failed with emerge.
One line did grab my attention: checking whether we are cross compiling... = no

Maybe the environment that i686-gentoo-linux-gnu-emerge creates i= s not working for ACE.

What do you think?

Regards,
Kfir
--001636831db291b64504942a44c2--