FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Embedded

 
 
LinkBack Thread Tools
 
Old 10-31-2010, 07:08 AM
Kfir Lavi
 
Default configu error: C++ compiler cannot create executables

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

It seems to me that my toolchain is not complete and the C++ compiler
was not created correctly.

How can I solve this problem?

Regards,
Kfir
 
Old 11-02-2010, 11:49 AM
Manuel Lauss
 
Default configu error: C++ compiler cannot create executables

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
 
Old 11-03-2010, 09:33 AM
Kfir Lavi
 
Default configu error: C++ compiler cannot create executables

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
 
Old 11-03-2010, 04:50 PM
Kfir Lavi
 
Default configu error: C++ compiler cannot create executables

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
 
Old 11-03-2010, 05:32 PM
Kfir Lavi
 
Default configu error: C++ compiler cannot create executables

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.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


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
 
Old 11-08-2010, 09:04 AM
Kfir Lavi
 
Default configu error: C++ compiler cannot create executables

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



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.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


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




I did again a cross compilation, really the same way I did before, but with a different name.
crossdev -P -vt i686-gentoo1-linux-gnu
But without the -S, so it compiled all the latest and greatest.


Now the problem is solved, but still ACE will stuck on another line:
checking for epoll_create... configure: error: cannot run test program while cross compiling
See `config.log' for more details.

But this is for different thread.


Regards,
Kfir
 
Old 12-05-2010, 06:52 PM
Enrico Weigelt
 
Default configu error: C++ compiler cannot create executables

* Kfir Lavi <lavi.kfir@gmail.com> schrieb:

> Now the problem is solved, but still ACE will stuck on another line:
> checking for epoll_create... configure: error: cannot run test program while
> cross compiling

They're using AC_TRY_RUN(), which is completely ridiculus.

File an upstream report.


cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/

phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
 
Old 12-23-2010, 03:43 PM
Kfir Lavi
 
Default configu error: C++ compiler cannot create executables

On Mon, Nov 8, 2010 at 12:04 PM, Kfir Lavi <lavi.kfir@gmail.com> wrote:



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




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.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


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





I did again a cross compilation, really the same way I did before, but with a different name.
crossdev -P -vt i686-gentoo1-linux-gnu
But without the -S, so it compiled all the latest and greatest.



Now the problem is solved, but still ACE will stuck on another line:
checking for epoll_create... configure: error: cannot run test program while cross compiling
See `config.log' for more details.

But this is for different thread.



Regards,
Kfir

I have created an ebuild that deletes the epoll test from configure.
I have posted it here: http://bugs.gentoo.org/show_bug.cgi?id=348521

After eliminating the epoll test, the compilation passes.

Regards,
Kfir
 
Old 12-30-2010, 05:27 AM
Enrico Weigelt
 
Default configu error: C++ compiler cannot create executables

* Kfir Lavi <lavi.kfir@gmail.com> schrieb:

> I have created an ebuild that deletes the epoll test from configure.
> I have posted it here: http://bugs.gentoo.org/show_bug.cgi?id=348521
> After eliminating the epoll test, the compilation passes.

Patching autogenerated files is not a good idea - change the
actual source and regenerate.


cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/

phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
 
Old 12-30-2010, 11:21 AM
Kfir Lavi
 
Default configu error: C++ compiler cannot create executables

On Thu, Dec 30, 2010 at 8:27 AM, Enrico Weigelt <weigelt@metux.de> wrote:


* Kfir Lavi <lavi.kfir@gmail.com> schrieb:



> I have created an ebuild that deletes the epoll test from configure.

> I have posted it here: http://bugs.gentoo.org/show_bug.cgi?id=348521

> After eliminating the epoll test, the compilation passes.



Patching autogenerated files is not a good idea - change the

actual source and regenerate.


In the ACE files they ask not to generate configure alone. So I tried it But had problem to finish.
My guess they still tweak by hand.
This is why I went to the auto-generated file. Not the best, but solves the problem for now.*



Kfir



cu

--

----------------------------------------------------------------------

*Enrico Weigelt, metux IT service -- http://www.metux.de/



*phone: *+49 36207 519931 *email: weigelt@metux.de

*mobile: +49 151 27565287 *icq: * 210169427 * * * * skype: nekrad666

----------------------------------------------------------------------

*Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme

----------------------------------------------------------------------
 

Thread Tools




All times are GMT. The time now is 06:56 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org