> Funny, I've been meaning to write in on this.
>
> I hit this problem hard too. I was linking the GHC compiler to a C
> library. I compiled the whole compiler with -prof, but whenever it
> called into the C library it would core dump. For a long time
> (years!) I assumed it was something strange my C library was
> doing. Last week I finally tracked it down. I was linking in the
> HDirect library to interface to C and of course that hadn't been
> compiled with -prof.
>
> Mercury adds an extra symbol to the rts and any modules not compiled
> with -prof cause a link error. Fergus tells me that it gives a very
> nice error, but a quick look at the Mercury documentation didn't find
> it. If you want more info just mail me.
>
> But PLEASE DO IT!!!
Ok, ok :-)
For the historians out there, we actually used to have such a feature in
the driver called "link-checking" which checked that the object files
being linked together were actually compatible. This stopped working at
some point and no-one got around to fixing it.
I like the idea of having a symbol in the RTS representing the "way",
that every module links to; I'll try that approach.
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
