Sven Panne on:
> > Warning: Linking some objects which contain exception information sections
> > and some which do not. This may cause fatal runtime exception
handling
> > problems (last obj encountered without exceptions was
main/LoopHack.o).
> I don't speak DECish too fluently, but here's my humble guess:
> Under arcane circumstances, linking gcc-compiled code on DEC-Unix 3.2
> produces the above warning. It's annoying, but it doesn't hurt (at least
> apart from aesthetics :-) .
I can now concur, as the rest of the build went swimmingly. Perhaps
Josh's problems were 3.2 specific... I don't know if 3.2 and 4.0
are alleged to be object code compatible -- if so, and anyone's
desparate enough to try, I could perhaps arrange to send them a built
hsc.
More utterances: I also note the following message from later in
said build. I can't recall having seen any such things things before,
though perhaps I either didn't do builds on other platforms with
-dshow-passes set (or just didn't notice the output if I did). I assume
it too is benign, just mildly Mysterious to we mere mortals.
Cheers,
Alex.
--
rm -f src/PosixUtil.p_o ; if [ ! -d src/PosixUtil ]; then mkdir src/PosixUtil ;
else exit 0; fi; find src/PosixUtil -name '*.p_o' -print | xargs rm -f
__rm_food;
../../ghc/driver/ghc -H50M -K8M -split-objs -odir src/PosixUtil -hisuf p_hi
-recomp -isrc -cpp -fvia-C -fglasgow-exts -dcore-lint -prof
'-#include"cbits/libposix.h"' -monly-3-regs -dshow-passes -c src/PosixUtil.lhs
-o src/PosixUtil.p_o -osuf p_o
ghc: WARNING: splitting objects when profiling will *BREAK* if any _scc_s are
present!
*** Reader:
*** Renamer:
*** TypeCheck:
*** DeSugar:
*** Core2Core:
*** Core2Core: Simplify
*** Core2Stg:
*** Stg2Stg:
*** Core Lint result of TidyCorePgm
*** Core Lint result of Simplify (3)
*** CodeGen:
ghc: module version changed to 1; reason: no old .hi file
