Re: [gentoo-user] Failed to emerge sys-devel/gcc-4.4.5

[Pandu Poluan <pandu@poluan.info>]

On Mon, Apr 4, 2011 at 19:34, Mike Edenfield <kutulu@kutulu.org> wrote:
> On 4/4/2011 8:07 AM, Pandu Poluan wrote:
>
>> MAKEOPTS="-j3"
>
>> {standard input}: Assembler messages:
>> {standard input}:146362: Error: open CFI at the end of file; missing
>> .cfi_endproc directive
>> xgcc: Internal error: Killed (program cc1)
>
> This kind of error is often caused by the parallel make not quite working.
> Try running the build like:
>
> MAKEOPTS="-j1" emerge =sys-devel/gcc-4.4.5
>
> In general, whenever you get strange build errors (i.e. that have no
> immediately obvious cause) you should try again with MAKEOPTS="-j1". Often
> it will fix the problem, but even when it doesn't you will usually get a
> much more useful error.

Thanks for the tip. Now it's 'partially successful':

 * QA Notice: Package has poor programming practices which may compile
 *            fine but exhibit random runtime failures.
 * /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/libgcc/../gcc/unwind-dw2-fde.c:321:
warning: dereferencing type-punned pointer will break strict-aliasing
rules

[-- snipped: a whole lotta warning for unwind-dw2-fde.c --]

 * /var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/libgcc/../gcc/unwind-dw2-fde.c:843:
warning: dereferencing type-punned pointer will break strict-aliasing
rules

 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: http://gcc.gnu.org/

>>> Installing (1 of 1) sys-devel/gcc-4.4.5
 * gcc-config: Could not locate 'x86_64-pc-linux-gnu-4.4.4' in
'/etc/env.d/gcc/' !
 * Running 'fix_libtool_files.sh 4.4.4'
 * Scanning libtool files for hardcoded gcc library paths...
cat: ld.so.conf.d/*.conf: No such file or directory
gcc-config: error: could not run/locate 'gcc'
:0: assertion failed: (gcc -dumpversion) | getline NEWVER)
 * Switching native-compiler to x86_64-pc-linux-gnu-4.4.5 ...

 * Your gcc has a bug with GCC_SPECS.
 * Please re-emerge gcc.
 * http://bugs.gentoo.org/68395

>>> Regenerating /etc/ld.so.cache...                                                                                                                   [ ok ]

 * If you intend to use the gcc from the new profile in an already
 * running shell, please remember to do:

 *   # source /etc/profile


 * If you have issues with packages unable to locate libstdc++.la,
 * then try running 'fix_libtool_files.sh' on the old gcc versions.

 * You might want to review the GCC upgrade guide when moving between
 * major versions (like 4.2 to 4.3):
 * http://www.gentoo.org/doc/en/gcc-upgrading.xml


 * Messages for package sys-devel/gcc-4.4.5:

 * If you have issues with packages unable to locate libstdc++.la,
 * then try running 'fix_libtool_files.sh' on the old gcc versions.
 * You might want to review the GCC upgrade guide when moving between
 * major versions (like 4.2 to 4.3):
 * http://www.gentoo.org/doc/en/gcc-upgrading.xml
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.
 * After world updates, it is important to remove obsolete packages with
 * emerge --depclean. Refer to `man emerge` for more information.

As instructed, I'll now re-emerge gcc.

Rgds,
--
Pandu E Poluan
~ IT Optimizer ~
Visit my Blog: http://pepoluan.posterous.com