Re: Undefined symbols on new install of ghc 6.2.2

Puzzling; couple of things to check for:

- nm -o c:/ghc/ghc-6.2.2/libHSbase.a | grep 'T ___stginit_Prelude'

 is successful.

- the TMPDIR setting appears to be w:/tmp -- make sure that actually
 exists & isn't clogged up. Does changing it to "." (or somesuch) alter
 the behaviour?

- does an invocation of the form "ghc -o build.exe MakeUtils.o Build.o 
<whatever else>"
 succeed?

--sigbjorn

----- Original Message ----- 
From: "Alastair Reid" <Alastair.Reid@xxxxxxx>
To: <glasgow-haskell-bugs@xxxxxxxxxxx>
Sent: Wednesday, August 17, 2005 05:59
Subject: Undefined symbols on new install of ghc 6.2.2


One of my colleagues just installed ghc 6.2.2 on their Windows machine.
GHC compiles fine but ghc --make fails at the linking stage with a bunch
of undefined symbols that ought to have been part of the ghc install
like:

./MakeUtils.o(.text+0x43): In function `_stginit_MakeUtils_':
: undefined reference to `_stginit_IO_'
./MakeUtils.o(.text+0x4d): In function `_stginit_MakeUtils_':
: undefined reference to `_stginit_Prelude_'
./MakeUtils.o(.text+0x5c): In function `r1pU_srt':
: undefined reference to `GHCziBase_zdfEqZMZN_closure'

(see attached file for complete list of undefined symbols).

We've checked that the lib files exist and confirmed that he installed
ghc in the normal place (see message at end of this message).
ghc-6.2.2 works just fine on my machine.

Does this ring any bells for anyone?

--
Alastair Reid, Principal Engineer, R&D
ARM Ltd, 110 Fulbourn Rd, Cambridge, CB1 9NJ.
T: +44 1223 406 109

<yadda yadda>

-----Original Message-----

Alastair Reid wrote:
> Can you try:
>
>   ghc -v
>
> this will produce a few hundred lines of output amongst which
> there's a bunch of filenames like
>
>   c:/ghc/ghc-6.2.2
>   c:/ghc/ghc-6.2.2/imports
>   c:/ghc/ghc-6.2.2/hslibs-imports/util
>
> The first should have a bunch of files with names like
> libHS*.a and is the most important
> The latter should have a bunch of *.hi files (and seem to be
> fine since you got as far as linking).

Assuming you mean that these directories should have the files you name
(not the output of ghc -v), then, yes, they are present.

> Check you're not really low on diskspace in case the install
> silently failed (e.g., the 100s of Mbytes of libHS*.a files
> weren't all installed).

Plenty of disc space.

> If that looks plausible, try adding the -v flag to the ghc
> --make command line to see if you get any useful info about
> the failure.
> If still nothing, try -v4 and -v5 to get extra verbosity.

I tried this but learnt nothing new (see attached). Is it possible that
I need to set some environment variables other than PATH (e.g.
LD_LIBRARY_PATH)?