1 |
On Wed, Nov 3, 2010 at 12:33 PM, Kfir Lavi <lavi.kfir@×××××.com> wrote: |
2 |
|
3 |
> |
4 |
> |
5 |
> On Tue, Nov 2, 2010 at 2:49 PM, Manuel Lauss <manuel.lauss@××××××××××.com>wrote: |
6 |
> |
7 |
>> On Sun, Oct 31, 2010 at 9:08 AM, Kfir Lavi <lavi.kfir@×××××.com> wrote: |
8 |
>> > Hi, |
9 |
>> > I have a cross compilation environment inside a chroot. |
10 |
>> > I run: |
11 |
>> > i686-unknown-linux-gnu-emerge dev-libs/ace |
12 |
>> > ... |
13 |
>> > checking for i686-unknown-linux-gnu-g++... i686-unknown-linux-gnu-g++ |
14 |
>> > checking for C++ compiler default output file name... configure: |
15 |
>> > error: C++ compiler cannot create executables |
16 |
>> |
17 |
>> Have a look at config.log. It tells exactly what went wrong, including |
18 |
>> gcc |
19 |
>> error output. |
20 |
>> |
21 |
>> Manuel |
22 |
>> |
23 |
>> It seems that one of the steps that I do, is deleting the tools. I need |
24 |
> then to install again from package from the mother system (I'm running here |
25 |
> as chroot, and its very good that I did so). |
26 |
> So I install gcc and binutils, then compile them again in the chroot |
27 |
> environment. |
28 |
> Using i686-unknown-linux-gnu-emerge and everything happens again. |
29 |
> I didn't find the culprit yet. |
30 |
> |
31 |
> Kfir |
32 |
> |
33 |
|
34 |
It seems that installing dev-libs/ace is causing the problem. |
35 |
emerge dev-libs/ace [works] |
36 |
i686-gentoo-linux-gnu-g++ [works] |
37 |
i686-gentoo-linux-gnu-gcc [works] |
38 |
gcc [works] |
39 |
g++ [works] |
40 |
i686-gentoo-linux-gnu-emerge dev-libs/ace [DONT WORK] |
41 |
|
42 |
Other packages emerging ok with i686-gentoo-linux-gnu-emerge. |
43 |
Can someone give me a hint? or something to check? |
44 |
|
45 |
Thanks, |
46 |
Kfir |