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