groff/font/devX100 segfault in "make installworld"

Tom Trelvik ttt at cwru.edu
Tue Feb 8 13:33:36 PST 2005


	So I ran into this problem a few months ago when I first started 
setting up a couple new servers.  At the time I found one person online 
who'd had a very similar sounding problem some time before that, and he 
said it had gone away on its own for him, and that he suspected it was 
something corrupt in the source tree.  I moved /usr/src out of the way 
and tried to cvsup a fresh source tree, and things started working.

	But now, it looks like I had just gotten lucky somehow.  I've 
reinstalled one of those systems and the same issue cropped back up 
again, and I'm at a loss as to what to do about it this time.

	Pretty much all I did was install the "User" distribution set from 
5.3-RELEASE-amd64-miniinst.iso and then installed bash2, sudo, screen, 
vim (NO_GUI=yes), portupgrade, & cvsup-without-gui from ports (not that 
I expect those to matter, I'm just trying to be thorough since I did so 
little that I can think of that might affect this).

	I then created the following cvs-supfile:

$ cat /root/cvs-supfile
*default host=cvsup12.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_5_3
*default delete use-rel-suffix
*default compress
src-all
ports-all tag=.

	and ran the following commands:

# cd /usr/src && \
	cvsup -g -L 2 /root/cvs-supfile && \
	make buildworld && \
	make buildkernel KERNCONF=GENERIC && \
	make installkernel KERNCONF=GENERIC && \
	make installworld

	and the "make installworld" ends with this segfault:

===> gnu/usr.bin/groff/doc
install-info --quiet  --defsection=Miscellaneous  --defentry= 
groff.info /usr/s
hare/info/dir
install -o root -g wheel -m 444  groff.info.gz /usr/share/info
===> gnu/usr.bin/groff/font
===> gnu/usr.bin/groff/font/devX100
Segmentation fault (core dumped)
*** Error code 139

	I tried moving /usr/src out of the way again, and cvsup'ing a fresh 
source tree again, but to no avail, and I'm once again at a loss, and 
not really sure how to diagnose what's causing this.

	I don't suppose anyone has any suggestions or pointers?  Thanks a ton, 
I really appreciate it!

Tom



More information about the freebsd-questions mailing list