Re: linker error message

2007-05-13 Thread John Meacham
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
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs


Re: linker error message

2007-05-13 Thread Frederik Eaton
Hello,

Ah, removing the entire install directory for the package (in ~/lib/)
fixed things. That seems odd, but perhaps I should be doing it in my
Makefile.

Thanks,

Frederik

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...
> 
> Thanks,
> 
> Frederik
> 
> -- 
> http://ofb.net/~frederik/
> ___
> Glasgow-haskell-bugs mailing list
> Glasgow-haskell-bugs@haskell.org
> http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
> 

-- 
http://ofb.net/~frederik/
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs


RE: linker error

2003-02-03 Thread Simon Peyton-Jones
The desugarer generates tuples when desugaring mutually-recursive
functions, and I bet that is what is causing the problem.

These optimiser usually gets rid of them, as you found.

It's a known shortcoming which has never gotten high enough up the list
to solve.

Could you please keep the source code to use as a test case?  Then we
can check if we do fix it.  Ideally just send us a .hs file whose
compilation breaks.

Simon

| -Original Message-
| From: Andres Loeh [mailto:[EMAIL PROTECTED]]
| Sent: 29 January 2003 17:11
| To: [EMAIL PROTECTED]
| Cc: [EMAIL PROTECTED]
| Subject: linker error
| 
| Hi there,
| 
| while compiling the latest Generic Haskell version I got the following
| linker error:
| 
| UHA_Parser.o(.text+0x117f13): In function `r18Ks_entry':
| : undefined reference to `DataziTuple_Z94T_con_info'
| collect2: ld returned 1 exit status
| 
| 
| The file "UHA_Parser.hs" is a generated parser for the language, using
| Ralf Hinze's "frown" parser generator.
| 
| When I first saw the error, I expected that too large tuples might be
| used in that file (motivated by the undefined reference containing the
| work "Tuple" and the number "94", which is higher than the GHC maximum
| as declared in the User's guide), but browsing through the file it
| does not seem to make much use of tuples at all.
| 
| In the meantime I found out that using -O2 to compile UHA_Parser
| will circumvent the bug, so it is not really a problem.
| 
| The bug occurs with both yesterday's CVS 5.05 version and 5.04.
| 
| I can try to produce a better bug description by cutting down the size
| of the involved files at least a little bit, but I thought that maybe
| you already know where to look ...
| 
| Best,
|   Andres
| ___
| Glasgow-haskell-bugs mailing list
| [EMAIL PROTECTED]
| http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
___
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs