| 1 |
On Mon, Apr 4, 2011 at 19:34, Mike Edenfield <kutulu@××××××.org> wrote: |
| 2 |
> On 4/4/2011 8:07 AM, Pandu Poluan wrote: |
| 3 |
> |
| 4 |
>> MAKEOPTS="-j3" |
| 5 |
> |
| 6 |
>> {standard input}: Assembler messages: |
| 7 |
>> {standard input}:146362: Error: open CFI at the end of file; missing |
| 8 |
>> .cfi_endproc directive |
| 9 |
>> xgcc: Internal error: Killed (program cc1) |
| 10 |
> |
| 11 |
> This kind of error is often caused by the parallel make not quite working. |
| 12 |
> Try running the build like: |
| 13 |
> |
| 14 |
> MAKEOPTS="-j1" emerge =sys-devel/gcc-4.4.5 |
| 15 |
> |
| 16 |
> In general, whenever you get strange build errors (i.e. that have no |
| 17 |
> immediately obvious cause) you should try again with MAKEOPTS="-j1". Often |
| 18 |
> it will fix the problem, but even when it doesn't you will usually get a |
| 19 |
> much more useful error. |
| 20 |
|
| 21 |
Thanks for the tip. Now it's 'partially successful': |
| 22 |
|
| 23 |
* QA Notice: Package has poor programming practices which may compile |
| 24 |
* fine but exhibit random runtime failures. |
| 25 |
* /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/libgcc/../gcc/unwind-dw2-fde.c:321: |
| 26 |
warning: dereferencing type-punned pointer will break strict-aliasing |
| 27 |
rules |
| 28 |
|
| 29 |
[-- snipped: a whole lotta warning for unwind-dw2-fde.c --] |
| 30 |
|
| 31 |
* /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/libgcc/../gcc/unwind-dw2-fde.c:843: |
| 32 |
warning: dereferencing type-punned pointer will break strict-aliasing |
| 33 |
rules |
| 34 |
|
| 35 |
* Please do not file a Gentoo bug and instead report the above QA |
| 36 |
* issues directly to the upstream developers of this software. |
| 37 |
* Homepage: http://gcc.gnu.org/ |
| 38 |
|
| 39 |
>>> Installing (1 of 1) sys-devel/gcc-4.4.5 |
| 40 |
* gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.4.4' in |
| 41 |
'/etc/env.d/gcc/' ! |
| 42 |
* Running 'fix_libtool_files.sh 4.4.4' |
| 43 |
* Scanning libtool files for hardcoded gcc library paths... |
| 44 |
cat: ld.so.conf.d/*.conf: No such file or directory |
| 45 |
gcc-config: error: could not run/locate 'gcc' |
| 46 |
:0: assertion failed: (gcc -dumpversion) | getline NEWVER) |
| 47 |
* Switching native-compiler to x86_64-pc-linux-gnu-4.4.5 ... |
| 48 |
|
| 49 |
* Your gcc has a bug with GCC_SPECS. |
| 50 |
* Please re-emerge gcc. |
| 51 |
* http://bugs.gentoo.org/68395 |
| 52 |
|
| 53 |
>>> Regenerating /etc/ld.so.cache... [ ok ] |
| 54 |
|
| 55 |
* If you intend to use the gcc from the new profile in an already |
| 56 |
* running shell, please remember to do: |
| 57 |
|
| 58 |
* # source /etc/profile |
| 59 |
|
| 60 |
|
| 61 |
* If you have issues with packages unable to locate libstdc++.la, |
| 62 |
* then try running 'fix_libtool_files.sh' on the old gcc versions. |
| 63 |
|
| 64 |
* You might want to review the GCC upgrade guide when moving between |
| 65 |
* major versions (like 4.2 to 4.3): |
| 66 |
* http://www.gentoo.org/doc/en/gcc-upgrading.xml |
| 67 |
|
| 68 |
|
| 69 |
* Messages for package sys-devel/gcc-4.4.5: |
| 70 |
|
| 71 |
* If you have issues with packages unable to locate libstdc++.la, |
| 72 |
* then try running 'fix_libtool_files.sh' on the old gcc versions. |
| 73 |
* You might want to review the GCC upgrade guide when moving between |
| 74 |
* major versions (like 4.2 to 4.3): |
| 75 |
* http://www.gentoo.org/doc/en/gcc-upgrading.xml |
| 76 |
>>> Auto-cleaning packages... |
| 77 |
|
| 78 |
>>> No outdated packages were found on your system. |
| 79 |
|
| 80 |
* GNU info directory index is up-to-date. |
| 81 |
* After world updates, it is important to remove obsolete packages with |
| 82 |
* emerge --depclean. Refer to `man emerge` for more information. |
| 83 |
|
| 84 |
As instructed, I'll now re-emerge gcc. |
| 85 |
|
| 86 |
Rgds, |
| 87 |
-- |
| 88 |
Pandu E Poluan |
| 89 |
~ IT Optimizer ~ |
| 90 |
Visit my Blog: http://pepoluan.posterous.com |
Archives