From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] configure: error: C++ compiler cannot create executables
Date: Wed, 3 Nov 2010 12:33:26 +0200 [thread overview]
Message-ID: <AANLkTin7JXm1kU25bkaw_rvDDMkbDcymZd60TqgLMXue@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikJS0_TEtzfiyEfJ3WYqje=jMKw5CjefnAjioDK@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1459 bytes --]
next prev parent reply other threads:[~2010-11-03 11:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 8:08 [gentoo-embedded] configure: error: C++ compiler cannot create executables Kfir Lavi
2010-11-02 12:49 ` Manuel Lauss
2010-11-03 10:33 ` Kfir Lavi [this message]
2010-11-03 17:50 ` Kfir Lavi
2010-11-03 18:32 ` Kfir Lavi
2010-11-08 10:04 ` Kfir Lavi
2010-12-05 19:52 ` Enrico Weigelt
2010-12-23 16:43 ` Kfir Lavi
2010-12-30 6:27 ` Enrico Weigelt
2010-12-30 12:21 ` Kfir Lavi
2010-12-31 1:15 ` Enrico Weigelt
2010-12-31 17:07 ` Kfir Lavi
2011-01-02 22:38 ` Enrico Weigelt
2011-01-03 15:00 ` Peter Stuge
2011-02-05 15:16 ` Enrico Weigelt
2011-02-06 7:21 ` Mike Frysinger
2011-02-13 22:28 ` Enrico Weigelt
2011-02-14 5:30 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin7JXm1kU25bkaw_rvDDMkbDcymZd60TqgLMXue@mail.gmail.com \
--to=lavi.kfir@gmail.com \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox