Progress Update: 1. still working on clean testsuite outcome for GHC 7.10.3 (test failures are cosmetic, but still concerning) 2. $ORIGIN is used to facilitate installing multiple independent GHC's simultaneously. Is that relevant to SmartOS deployments? If not, I think I can do up a Makefile patch in PKGSRC to remove it. If so, should we consider having a handful of separate ghc-MAJOR.MINOR packages?
On Thu, Dec 24, 2015 at 9:19 AM Alain O'Dea <[email protected]> wrote: > Thank you Jonathan. > > I'll take a deeper look at how $ORIGIN is used in the GHC build and see > whether or not it can be substituted or disabled. > > Best, > Alain > On Thu, Dec 24, 2015 at 04:42 Jonathan Perkin <[email protected]> wrote: > >> * On 2015-12-22 at 23:00 GMT, Alain O'Dea wrote: >> >> > I'd like to assist with getting GHC 7.10.x in PKGSRC. >> > >> > Jonathan, I understand you got really close, but GHC 7.10 changed shared >> > library handling in a way that complicated things. I'm happy to debug >> and >> > chase down answers to that if that is useful. I imagine I'll learn a >> lot >> > in the process. >> >> The main issue is that the final ghc binary now links against a number >> of libraries in various directories under /opt/local/lib/ghc-$version, >> and handles this using the $ORIGIN feature of ld. We do not support >> $ORIGIN in pkgsrc, so there are three choices, in order of preference: >> >> - Wade through the ghc build infrastructure replacing use of $ORIGIN >> with full paths to the libraries in question using the normal rpath >> feature. >> >> - Figure out if it's possible to revert to the previous behaviour. >> >> - Support $ORIGIN in pkgsrc. >> >> The latter could actually be quite difficult, and probably wouldn't be >> a good first pkgsrc project as it will touch quite a bit of >> infrastructure, so maybe look at either of the first two and see if >> you can get any traction there. >> >> The way I got it somewhat working so far is to use the "static" >> linking build option (it isn't really, it just means for these >> problematic libraries), which results in a working ghc binary, however >> it breaks any haskell packages that build libraries as ghc-pkg can't >> find the core libraries. This may be a bug, I don't know. >> >> Thanks! >> >> -- >> Jonathan Perkin - Joyent, Inc. - www.joyent.com >> > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
