| 1 |
On Wed, Nov 3, 2010 at 7:50 PM, Kfir Lavi <lavi.kfir@×××××.com> wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> |
| 5 |
> On Wed, Nov 3, 2010 at 12:33 PM, Kfir Lavi <lavi.kfir@×××××.com> wrote: |
| 6 |
> |
| 7 |
>> |
| 8 |
>> |
| 9 |
>> On Tue, Nov 2, 2010 at 2:49 PM, Manuel Lauss <manuel.lauss@××××××××××.com |
| 10 |
>> > wrote: |
| 11 |
>> |
| 12 |
>>> On Sun, Oct 31, 2010 at 9:08 AM, Kfir Lavi <lavi.kfir@×××××.com> wrote: |
| 13 |
>>> > Hi, |
| 14 |
>>> > I have a cross compilation environment inside a chroot. |
| 15 |
>>> > I run: |
| 16 |
>>> > i686-unknown-linux-gnu-emerge dev-libs/ace |
| 17 |
>>> > ... |
| 18 |
>>> > checking for i686-unknown-linux-gnu-g++... i686-unknown-linux-gnu-g++ |
| 19 |
>>> > checking for C++ compiler default output file name... configure: |
| 20 |
>>> > error: C++ compiler cannot create executables |
| 21 |
>>> |
| 22 |
>>> Have a look at config.log. It tells exactly what went wrong, including |
| 23 |
>>> gcc |
| 24 |
>>> error output. |
| 25 |
>>> |
| 26 |
>>> Manuel |
| 27 |
>>> |
| 28 |
>>> It seems that one of the steps that I do, is deleting the tools. I need |
| 29 |
>> then to install again from package from the mother system (I'm running here |
| 30 |
>> as chroot, and its very good that I did so). |
| 31 |
>> So I install gcc and binutils, then compile them again in the chroot |
| 32 |
>> environment. |
| 33 |
>> Using i686-unknown-linux-gnu-emerge and everything happens again. |
| 34 |
>> I didn't find the culprit yet. |
| 35 |
>> |
| 36 |
>> Kfir |
| 37 |
>> |
| 38 |
> |
| 39 |
> It seems that installing dev-libs/ace is causing the problem. |
| 40 |
> emerge dev-libs/ace [works] |
| 41 |
> i686-gentoo-linux-gnu-g++ [works] |
| 42 |
> i686-gentoo-linux-gnu-gcc [works] |
| 43 |
> gcc [works] |
| 44 |
> g++ [works] |
| 45 |
> i686-gentoo-linux-gnu-emerge dev-libs/ace [DONT WORK] |
| 46 |
> |
| 47 |
> Other packages emerging ok with i686-gentoo-linux-gnu-emerge. |
| 48 |
> Can someone give me a hint? or something to check? |
| 49 |
> |
| 50 |
> Thanks, |
| 51 |
> Kfir |
| 52 |
> |
| 53 |
|
| 54 |
Some diagnostics: |
| 55 |
$ cd /usr/__CHOST__/tmp/portage/dev-libs/ace-5.7.2/work/ACE_wrappers/build |
| 56 |
$ ../configure |
| 57 |
checking build system type... i686-pc-linux-gnu |
| 58 |
checking host system type... i686-pc-linux-gnu |
| 59 |
checking target system type... i686-pc-linux-gnu |
| 60 |
checking for a BSD-compatible install... /usr/bin/install -c |
| 61 |
checking whether build environment is sane... yes |
| 62 |
checking for gawk... gawk |
| 63 |
checking whether make sets $(MAKE)... yes |
| 64 |
checking for egrep... grep -E |
| 65 |
checking whether #! works in shell scripts... yes |
| 66 |
checking for g++... g++ |
| 67 |
checking for C++ compiler default output file name... a.out |
| 68 |
checking whether the C++ compiler works... yes |
| 69 |
checking whether we are cross compiling... no |
| 70 |
checking for suffix of executables... |
| 71 |
checking for suffix of object files... o |
| 72 |
checking whether we are using the GNU C++ compiler... yes |
| 73 |
checking whether g++ accepts -g... yes |
| 74 |
checking for style of include used by make... GNU |
| 75 |
checking dependency style of g++... gcc3 |
| 76 |
checking how to run the C++ preprocessor... g++ -E |
| 77 |
|
| 78 |
Here we see that configure passes the test it failed with emerge. |
| 79 |
One line did grab my attention: checking whether we are cross compiling... |
| 80 |
no |
| 81 |
|
| 82 |
Maybe the environment that i686-gentoo-linux-gnu-emerge creates is not |
| 83 |
working for ACE. |
| 84 |
|
| 85 |
What do you think? |
| 86 |
|
| 87 |
Regards, |
| 88 |
Kfir |
Archives