I love useful errors from software. Too bad I never see any:
...
creating guile
cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc gc.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc hooks.doc init.doc ioext.doc iselect.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc strop.doc strorder.doc strports.doc struct.doc symbols.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc symbols-deprecated.doc ramap.doc unif.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc | GUILE="/home/jamie/compile/guile-1.6.7/pre-inst-guile" ../scripts/snarf-check-and-output-texi --manual > guile.texi || { rm guile.texi; false; }
ERROR: Stack overflow
gmake[2]: *** [guile.texi] Error 1
gmake[2]: Leaving directory `/usr/home/jamie/compile/guile-1.6.7/libguile'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/home/jamie/compile/guile-1.6.7'
gmake: *** [all] Error 2
11:45am ogre /home/jamie/compile/guile-1.6.7 %
Thanks. Which fucking piece of this bloated shit is overflowing the stack? I've increased both the overall system and per process stack size half an order of magnitude. How much fucking stack space does this goddamned piece of GNU shit need to build? And WHY? If you need that much stack space, you were obviously written by an idiot, and if I didn't fucking need you to compile GCC, I would already have deleted your worthless bits. The part that really annoys me is that I have no fucking clue which process is overflowing the stack. The possibilities, they are many: make, /bin/sh, texinfo, cat, rm, any of the processes called by the snarf-check-and-output-texi shell script...
I swear, I'm going to start killing people one day...
Soon.
...
creating guile
cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc gc.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc hooks.doc init.doc ioext.doc iselect.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc strop.doc strorder.doc strports.doc struct.doc symbols.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc symbols-deprecated.doc ramap.doc unif.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc | GUILE="/home/jamie/compile/guile-1.6.7/pre-inst-guile" ../scripts/snarf-check-and-output-texi --manual > guile.texi || { rm guile.texi; false; }
ERROR: Stack overflow
gmake[2]: *** [guile.texi] Error 1
gmake[2]: Leaving directory `/usr/home/jamie/compile/guile-1.6.7/libguile'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/home/jamie/compile/guile-1.6.7'
gmake: *** [all] Error 2
11:45am ogre /home/jamie/compile/guile-1.6.7 %
Thanks. Which fucking piece of this bloated shit is overflowing the stack? I've increased both the overall system and per process stack size half an order of magnitude. How much fucking stack space does this goddamned piece of GNU shit need to build? And WHY? If you need that much stack space, you were obviously written by an idiot, and if I didn't fucking need you to compile GCC, I would already have deleted your worthless bits. The part that really annoys me is that I have no fucking clue which process is overflowing the stack. The possibilities, they are many: make, /bin/sh, texinfo, cat, rm, any of the processes called by the snarf-check-and-output-texi shell script...
I swear, I'm going to start killing people one day...
Soon.