Bug 64677 – gcc-3.3.4-r1 fails to compile; Failed Patch: pro-police-docs.patch!

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description David Oberlitner 2004-09-19 14:07:37 UTC]

# uname -a 
Linux asp2 2.4.26-sparc-r2 #2 SMP Thu Jul 1 21:38:04 MDT 2004 sparc64 sun4u TI UltraSparc II  (BlackBird) GNU/Linux
# gcc -v 
....
gcc version 3.3.3 20040217 (Gentoo Linux 3.3.3, propolice-3.3-7)
# emerge -uv system
....
* Applying gcc331-pp-fixup.patch...            [ ok ]
* Applying gcc333-ssp-3.3.2_1-fixup.patch...   [ ok ]
* Applying protector.dif...                    [ ok ]
* Applying pro-police-docs.patch...

* A dry-run of patch command succeeded, but actually
* applying the patch failed!

* Failed Patch: pro-police-docs.patch!
*
* Include in your bugreport the contents of:
*
*   /var/tmp/portage/gcc-3.3.4-r1/temp/pro-police-docs.patch-16849.out

!!! ERROR: sys-devel/gcc-3.3.4-r1 failed.
!!! Function epatch, Line 404, Exitcode 0
!!! Failed Patch: pro-police-docs.patch!

All subsequent attempts yield the following error:
# emerge -uv system
....
gcc   -O -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long   -DHAVE_CONFIG_H -DGENERATOR_FILE  -o gengtype \
 gengtype.o gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a
./genpreds > tmp-preds.h
make[2]: *** [s-preds] Error 137
make[2]: *** Waiting for unfinished jobs....
rm -f gcc.pod
make[2]: Leaving directory `/var/tmp/portage/gcc-3.3.4-r1/work/build/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.3.4-r1/work/build/gcc'
make: *** [bootstrap-lean] Error 2

!!! ERROR: sys-devel/gcc-3.3.4-r1 failed.
!!! Function src_compile, Line 551, Exitcode 2
!!! (no error message)

See Attachments

Reproducible: Always
Steps to Reproduce:
1. # emerge -uv system => Patch Fail
2. # emerge -uv system => Compile Fail
3. # Repeated on two Sparc Ultra 2E's


Actual Results:  
Error messeages detailed above

Expected Results:  
Compiled without error

[Comment 1 David Oberlitner 2004-09-19 14:09:35 UTC]

Created attachment 39952 [details]
emerge STDOUT error message requested attachment

[Comment 2 Gustavo Zacarias (RETIRED) 2004-11-01 11:41:21 UTC]

Did you manage to upgrade to gcc-3.3.4-r1?
It was probably a broken patch in one of the mirrors, so a sync/retry should have fixed it...

[Comment 3 David Oberlitner 2004-11-01 15:14:20 UTC]

No direct success. Thanks for the inquiry. 

My latest attempt after a fresh "emerge sync" continues to yield gcc errors. In an attempt to update portage as a prerequisite I get the following snippet when processing gettext-0.12.1 after patches:

checking for sparc-unknown-linux-gnu-gcc... gcc
checking for C compiler default output... configure: error: C compiler cannot create executables
See `config.log' for more details.
configure: error: /bin/sh './configure' failed for autoconf-lib-link

In the meantime I bootstrapped another Ultra 2E without a hitch. I swapped disks from the development box to a production box and have been successful. I plan to update two additonal production boxes in the same manner.

I do not understand what actions induced my gcc problems. The newly bootstrapped system provides me with a suitable workaround. I now plan to upgrade my remaining production U2E's with the new system. 

This bug can be closed/resolved on my account. What follow-up action should I take?

Thanks for your help.

[Comment 4 Gustavo Zacarias (RETIRED) 2004-11-02 05:00:55 UTC]

Yeah, sorry for the delay in following this up, our workload was quite high.
To fix the machine, if they're running the same settings (mostly CFLAGS, CXXFLAGS & USE) you can "quickpkg gcc" and place the resulting tbz2 in /usr/portage/packages/All and do an emerge -k gcc on the offending machine.

[Comment 5 Jeremy Huddleston (RETIRED) 2005-01-10 03:59:00 UTC]

closing due to lack of response.  Please reopen if you need further help.