1 |
On Tue, Apr 5, 2011 at 21:42, Mike Edenfield <kutulu@××××××.org> wrote: |
2 |
> On 4/5/2011 3:03 AM, Pandu Poluan wrote: |
3 |
>> On Mon, Apr 4, 2011 at 19:34, Mike Edenfield <kutulu@××××××.org> wrote: |
4 |
>>> On 4/4/2011 8:07 AM, Pandu Poluan wrote: |
5 |
>>> |
6 |
>>>> MAKEOPTS="-j3" |
7 |
>>> |
8 |
>>>> {standard input}: Assembler messages: |
9 |
>>>> {standard input}:146362: Error: open CFI at the end of file; missing |
10 |
>>>> .cfi_endproc directive |
11 |
>>>> xgcc: Internal error: Killed (program cc1) |
12 |
>>> |
13 |
>>> This kind of error is often caused by the parallel make not quite working. |
14 |
>>> Try running the build like: |
15 |
>>> |
16 |
>>> MAKEOPTS="-j1" emerge =sys-devel/gcc-4.4.5 |
17 |
>>> |
18 |
>>> In general, whenever you get strange build errors (i.e. that have no |
19 |
>>> immediately obvious cause) you should try again with MAKEOPTS="-j1". Often |
20 |
>>> it will fix the problem, but even when it doesn't you will usually get a |
21 |
>>> much more useful error. |
22 |
>> |
23 |
>> Thanks for the tip. Now it's 'partially successful': |
24 |
>> |
25 |
>> * QA Notice: Package has poor programming practices which may compile |
26 |
>> * fine but exhibit random runtime failures. |
27 |
> |
28 |
> These aren't anything to worry about. |
29 |
> |
30 |
|
31 |
Thanks for the explanation :-) |
32 |
|
33 |
>>>>> Installing (1 of 1) sys-devel/gcc-4.4.5 |
34 |
>> * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.4.4' in |
35 |
>> '/etc/env.d/gcc/' ! |
36 |
>> * Running 'fix_libtool_files.sh 4.4.4' |
37 |
>> * Scanning libtool files for hardcoded gcc library paths... |
38 |
>> cat: ld.so.conf.d/*.conf: No such file or directory |
39 |
>> gcc-config: error: could not run/locate 'gcc' |
40 |
>> :0: assertion failed: (gcc -dumpversion) | getline NEWVER) |
41 |
>> * Switching native-compiler to x86_64-pc-linux-gnu-4.4.5 ... |
42 |
>> |
43 |
>> * Your gcc has a bug with GCC_SPECS. |
44 |
>> * Please re-emerge gcc. |
45 |
>> * http://bugs.gentoo.org/68395 |
46 |
> |
47 |
> All of this is caused by your previous gcc profile being invalid, that |
48 |
> is, pointing to a non-existent gcc version (one that had already been |
49 |
> uninstalled). You *don't* have to re-emerge gcc as it says -- the bug is |
50 |
> not in your GCC_SPECS but in gcc-config. |
51 |
> |
52 |
> You should first run gcc-config again to make sure your newly installed |
53 |
> compiler it set as the default, then run `fix_libtool_files.sh 4.4.4` as |
54 |
> the ebuild was trying to do. |
55 |
> |
56 |
|
57 |
And you had to reply *after* gcc is re-emerged >.< |
58 |
|
59 |
Oh well, good to know, anyways... prevent more griefs in the future :-) |
60 |
|
61 |
|
62 |
Rgds, |
63 |
-- |
64 |
Pandu E Poluan |
65 |
~ IT Optimizer ~ |
66 |
Visit my Blog: http://pepoluan.posterous.com |