On Mon, May 14, 2007 at 01:26:05AM +0100, Frederik Eaton wrote:
> Hello,
>
> Here is another (hopefully less bogus) error message which I don't
> know what to do with:
>
> $ A=bayesian-sets; ghc --make $A.hs -package vectro -lstdc++
> -fallow-incoherent-instances -lstdc++ && time ./$A
> [1 of 1] Compiling Main ( bayesian-sets.hs, bayesian-sets.o )
> Loading package base ... linking ... done.
> Loading package mtl-1.0 ... linking ... done.
> Loading package haskell98 ... linking ... done.
> Loading package X11-1.2 ... linking ... done.
> Loading package template-haskell ... linking ... done.
> Loading package stm-2.0 ... linking ... done.
> Loading package parsec-2.0 ... linking ... done.
> Loading package network-2.0 ... linking ... done.
> Loading package futility-base-0.1.9 ... linking ... done.
> Loading package unix-1.0 ... linking ... done.
> Loading package futility-unix-0.1.9 ... linking ... done.
> ghc-6.6.20070420:
> /home/frederik/lib/vectro-0.2/ghc-6.6.20070420/HSvectro-0.2.o: unknown symbol
> `vectrozm0zi2_VectorziBase_polyzuzuzu_closure'
> Loading package vectro-0.2 ... linking ... ghc-6.6.20070420: unable to load
> package `vectro-0.2'
>
> It seems that linker errors are a large class of errors which I
> semi-frequently get from GHC, and which are very difficult to
> interpret...
Yes, I quite regularly get odd linker messages too when working on large
projects like jhc. I have never been able to figure out a definite
pattern, touching the files involved and rebuilding fixes the issue in
general, I think there must be an odd race condition somewhere when
checking if .o files are up to date. it seems to happen much more
commonly the larger the program you are compiling is, so perhaps it has
something to do with the rather large lag between the time ghc parses
the files and actually uses the results of the parse to compile the .o
file. which can easily be tens of minutes for a large project. This is
just supposition though.
John
--
John Meacham - ⑆repetae.net⑆john⑈
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
