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