changes to the ebuild include: - ghc-6.4 (or ghc-bin-6.4) required - pugs does NOT run on amd64 because of a broken ghc - eventhough it compiles well. This error has been fixed in CVS but I could not find a patch for it. - integrates with parrot-0.2.0-r1 (will make this optional in the future) - version bump (a lot of new features !) Please report if this runs on x86. I plan to integrate hs-plugins as soon as they become available for ghc-6.4
Created attachment 59813 [details] pugs-6.2.5.ebuild
Created attachment 60455 [details] pugs-6.2.6.ebuild Please note that this also does not work on amd64 since ghc is broken
Created attachment 61168 [details] pugs-6.2.7.ebuild Yet another version of pugs - still broken because of the ghc-6.4 problem on amd 64. Seems to me to compile forever - parrot compiles faster - good, plain, old C ...
Created attachment 62484 [details] disables parrot linking The linking to parrot is broken in this release. I thought that the linking of the executables is not working on amd64 but the parrot team changed some things in parrot-0.2.1 that this pugs release is not aware of. Things should be in sync again when pugs-6.2.8 and parrot-0.2.2 come out (will be soon). As long as the ghc-6.4.1 is not out you won`t be able to use the current pugs on amd64.
Oddly enough, I'd begun to suspect parrot as well - it passed tests, but I was getting errors attempting to use the japh example set. parrot-0.2.2 was announced this morning, just waiting for it to show up on pause. :)
Definitely missing a lot with the parrot build...looking at the spec, I see the missing imcc materials being compiled, going to redo the parrot ebuild a bit before tackling pugs again (because i think it's a broken imcc compiler that's breaking the pugs build to begin with).
So you have problems compiling pugs? My problems start when linking the object files and I am not sure if this might be an imcc problem. I will wait for the new parrot release and see if it works there - this ist still beta software after all.
dies in the same spot, and the new parrot is out :)
I messed around with it yesterday and figured out that the mistake is in the parrot-0.2.2 Makefile "make install". Some files are missing and this is why it does not work. If you take parrot and build it from sources yourself (without make install) and give this to pugs there is no problem at all with the parrot integration. Leo wrote me that they will not worry about this right now and might do it after the next release. The new parrot (0.2.2) works with the same ebuild. I won`t post new ebuilds here until this error is fixed in parrot because it does not make sense at this point. Also there is still the ghc issue so I can`t test pugs even if it compiles.
The problem has been resoved. See http://bugs.gentoo.org/show_bug.cgi?id=101858 for a new ebuild + version of parrot (0.2.3). I will be working on a new ebuild for pugs to make use of this and post here when I am done.
I tried to get pugs working but got the following error Generating precompiled Prelude... pugs: internal error: scavenge_one: strange object 68 Please report this as a bug to glasgow-haskell-bugs@haskell.org, or http://www.sourceforge.net/projects/ghc/ system: [/usr/bin/perl5.8.5 util/gen_prelude.pl -v -i src/perl6/Prelude.pm -p ./pugs --touch --output src/Pugs/PreludePC.hs]: at util/build_pugs.pl line 65. make: *** [pugs] Error 1 It might relate to amd64 issues with ghc-6.4. Please try this ebuild and tell me if it works for you. DO NOT forget to update to parrot-0.2.3 first (see link above).
Created attachment 65762 [details] pugs-6.2.9.ebuild
all set
