On Mon, Mar 31, 2003 at 03:08:04PM +0100, Simon Marlow wrote: > Ok, I've done that. I'd be interested to know if GHCi on the HEAD > now works for people with this problem.
I'll give it a spin. > > If you call the linker through gcc, I would expect it to > > automatically add libgcc.a when necessary, unless told not to. I > > assume you have your reasons for linking the way you do, however. > > Yes, the problem is our dynamic linker which can only get access to > (a) symbols it knows about from objects it loaded and (b) symbols > from other dynamic libraries. These libgcc symbols are statically > linked, so they need to be listed explicitly in the linker's symbol > table. This is kind of an ugly wart, but there doesn't seem to be > an easy way around it. So my question is: why aren't HSBase_cbits.o, etc., _statically_ linked with libgcc? Then you wouldn't have to worry at all about this, right? -- Aaron Denney -><- _______________________________________________ Glasgow-haskell-bugs mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
