RE: GHC 5.02.2 installation/compilation problems
Hi Nick,
I just installed GHC 5.02.2 (actually, the latest version from CVS), and had a strange problem. My first attempt worked ok, but I screwed something up, so I junked it and started again from scratch.
This time, it died part-way through the "make boot" step for ghc itself, because glafp-utils/mkdependC/mkdependC had not been built. To fix the problem I just went to that directory and made mkdependC myself first, and then recompiled from $(BUILD), which worked. Does anyone have any idea why mkdependC may not have been built in the first place?
Nothing springs to mind, unless you had explicitly set $(ProjectsToBuild) in your build.mk, and left out glafp-utils. It usually isn't necessary to set $(ProjectsToBuild) as it defaults to building all the projects in the current tree.
Also, when I try to compile for ticky-ticky profiling by setting GhcCompilerWays=t and GhcLibWays=t in $(BUILD)/mk/build.mk, and then running "make all" in $(BUILD), it compiles for a short time and then dies with this error message:
Just set GhcLibWays=t, you don't have to set GhcCompilerWays too (this is for building the compiler itself in a different way). Cheers, Simon
On Fri, 25 Jan 2002, Simon Marlow wrote:
Nothing springs to mind, unless you had explicitly set $(ProjectsToBuild) in your build.mk, and left out glafp-utils. It usually isn't necessary to set $(ProjectsToBuild) as it defaults to building all the projects in the current tree.
Aha, that would be it, I had omitted glafp-utils from $(ProjectToBuild). Although I thought I had done it that way before... no matter.
Also, when I try to compile for ticky-ticky profiling...
Just set GhcLibWays=t, you don't have to set GhcCompilerWays too (this is for building the compiler itself in a different way).
Unless I want to ticky-ticky profile the compiler itself, yes? -- Nick Nethercote njn25@cam.ac.uk
On Fri, 25 Jan 2002, Nicholas Nethercote wrote:
Also, when I try to compile for ticky-ticky profiling...
Further in the ticky-ticky adventure... Having compiled the libraries and RTS and other bits for ticky-ticky, when I try the -ticky option with ghc I get loads of messages like this at link-time: /homes/njn25/ws/build/ghc/driver/../rts/libHSrts_t.a(GC.t_o): In function `threadSqueezeStack': GC.t_o(.text+0x2fe0): undefined reference to `LDV_recordDead_FILL_SLOP_DYNAMIC' GC.t_o(.text+0x3010): undefined reference to `LDV_recordCreate' GC.t_o(.text+0x304d): undefined reference to `LDV_recordCreate' These LDV_* functions seem to only be needed/used if compiling for normal profiling, which I'm not and don't want to. Similarly, when I try recompiling the RTS (trying to make the problem disappear), I get warnings of this sort: In file included from Updates.hc:14: Storage.h: In function `updateWithPermIndirection': Storage.h:289: warning: implicit declaration of function `LDV_recordDead_FILL_SLOP_DYNAMIC' So it seems PROFILING is being defined, but I'm not sure where since my $(BUILD)/mk/builk.mk file has these lines: GhcCompilerWays= GhcLibWays=t Can anyone suggest what might be causing the problem? Thanks. -- Nick Nethercote njn25@cam.ac.uk
participants (2)
-
Nicholas Nethercote -
Simon Marlow