Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Pugs now require GHC 6.4, so we're finally out from the #ifdef hell.

    This was the last one in a sequence of events that got me to the point of being unable to build Pugs from this forth.

    It started with the recent development of compiling Parse.hs with GHC requring about 220 MB of memory that immediately put all my PCs at home out of business. My last chance was a Linux server at work, but it comes with GHC 6.2 and I have no chance to get the sysadmins upgrade it (it even was a huge win to at least convince them to install ghc for me...).

    I see that Pugs now have nice Debian build scripts. Couldn't you make somehow nightly binary snapshots available as debian packages?

    thanks: rg0now

    • Please ask scw on IRC about the debian snapshots.

      Also, for your PCs, I have just committed a "make unoptimized" flag that should make it much happier. Let me know if it works or not. :)

      • For me at least, "make unoptimized" does not seem to impact the memory requirements of compiling Pugs (it still uses some 200 MB RAM every now and then), however, upgrading to ghc6-4 (as of Debian experimental) and to a more stable Linux kernel (from a highly experimental Con Kolivas patch set) definitely do: I can now compile Pugs at home. Thank you autrijus!

        p.s.: it appears that Parse.hs and Eval.hs (not sure about this) are the most demanding files, and as Pugs evolves, it will just get even worse. May