[Bug 70302] Re: no ghci in edgy (regression vs dapper)

I know this is pending on upstream & Debian activity, but just for the record this bug is still current on gutsy/powerpc. -- no ghci in edgy (regression vs dapper) https://bugs.launchpad.net/bugs/70302 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug co

[Bug 70302] Re: no ghci in edgy (regression vs dapper)

As long as GHC has no registerised-powerpc maintainer (which I believe is still true), and ghc bug #631 remains unfixed (even if it is fixed in GHC 6.8, that won't be out in time for Gutsy, but 6.8 will be in time for gutsy+1), I don't think this bug

[Bug 70302] Re: no ghci in edgy (regression vs dapper)

Hey folks. Is anyone still hoping to do something about this issue? Or should we mark it as "won't fix"? -- no ghci in edgy (regression vs dapper) https://bugs.launchpad.net/bugs/70302 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubunt

[Bug 70302] Re: no ghci in edgy (regression vs dapper)

Hi, ghc6 on powerpc is not built registerized: "Removed powerpc from the list of arches to do a registerised build with object splitting as there are bootstrapping issues from earlier GHCs." (Ian's changelog entry, 6.4-3). You can also find this out by looking at debian/rules of the sourcepacka

[Bug 70302] Re: no ghci in edgy (regression vs dapper)

Rebooting into a copy of my OS from before upgrading from Dapper to Edgy, I can reproduce the referenced ghc-bug-631. So I see there is a reason for this. On the other hand, I didn't notice any problems when I used ghci, personally... -- no ghci in edgy (regression vs dapper) https://launchpad.

[Bug 70302] Re: no ghci in edgy (regression vs dapper)

It's powerpc -- but surely GHC is built registerised on that architecture? (is there some way I can find out whether a given ghc binary was built that way?) -- no ghci in edgy (regression vs dapper) https://launchpad.net/bugs/70302 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https:

[Bug 70302] Re: no ghci in edgy (regression vs dapper)

Hi, what arch are you trying to use ghci on? (I'd guess it's neither i386 nor amd64). If so, it's intended that there is no more ghci, due to http://hackage.haskell.org/trac/ghc/ticket/631 . Backporting ghc6.6 is not trivially done, the same comments I wrote on bug #56516 apply here as well :(.

[Bug 70302] Re: no ghci in edgy (regression vs dapper)

Oops, I meant runhugs -98, not +98 -- its flags are so confusing. Probably this should be in a separate bug report somewhere, but, here is the messages I get for doing that the wrong way: runhugs: Error occurred ERROR "/usr/lib/hugs/libraries/Text/ParserCombinators/ReadP.hs":133 - Syntax error