Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 43106 - "emerge system" crashed while building groff (r1 to r4)
Summary: "emerge system" crashed while building groff (r1 to r4)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Hardened (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: The Gentoo Linux Hardened Team
URL:
Whiteboard:
Keywords:
: 43743 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-02-27 09:17 UTC by Jesús Menchaca
Modified: 2004-03-12 18:06 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesús Menchaca 2004-02-27 09:17:58 UTC
I am building my gentoo system, I built from Stage 1 and currently am at stage2, when I tried "emerge system", groff-1.18.1-r4 begins building, but when it gets to /var/tmp/portage/groff-1.18.1-r4/work/groff-1.18.1/contrib/mom it crashes with
"Make[2]: ***[examples/letter.ps] Error 139"
The "command" it tries to execute is something like this
*3 lines of code* -Tps -mom examples/letter.mom >examples/letter.ps
Is there a way I can fix this, or any way I can skip building groff?

Reproducible: Always
Steps to Reproduce:
1.partitioned my hd, extracted stage1(v2004), extracted snapshot(v2004), bootstrapped system
2.executed "emerge system" at command line
3.

Actual Results:  
Make[2]: *** [examples/letter.ps] Error 139
!!! ERROR: sys-apps/groff-1.18.1-r4 failed
!!! Function src_compile, Line 56, Exitcode 2
!!! (no error message)

Expected Results:  
I expected "emerge system" to complete successfully
Comment 1 Bryan Duff 2004-02-27 09:31:15 UTC
run 'etc-update'
update hcc file.
then run
'hcc -a'

That should fix the problem.
Comment 2 SpanKY gentoo-dev 2004-03-02 13:14:53 UTC
found an user on irc who had this problem and the proposed commands by Bryan fixed it for him
Comment 3 Neil Katin 2004-03-02 17:07:12 UTC
I had identical symptoms during my install of the 2004.0 livecd.
I'll point out that hardened-gcc had installed just before the
groff.

I can also confirm that the workaround "fixed" the problem for me.

The suggests to me that an emerge of the hardened-gcc package should
either automatically merge/run hcc (this is probably a bad idea) or
should just abort the emerge, so allow someone to manually follow
the instructions that are already at the end of the hardeneded-gcc
ebuild ("run etc-update, then hardened-gcc -A").

Since hardened-gcc has made it into the base system, should the component
be "ebuild" instead of "hardened" on this bug?



Comment 4 Sebastian Spaeth 2004-03-03 01:34:06 UTC
I although experienced this with a 2004.0 stage1 install. After the hcc.conf files were merged, and a hcc -a was issued, everything went ok. So this is definitive the right fix during the bootstrap process.
Comment 5 SpanKY gentoo-dev 2004-03-04 20:55:14 UTC
*** Bug 43743 has been marked as a duplicate of this bug. ***
Comment 6 Brandon Hale (RETIRED) gentoo-dev 2004-03-12 18:06:24 UTC
hardened-gcc is now masked, and the hardened stages are moved out of the way. this problem shouldnt crop up again.