One of things I were afraid of was that I did not understand the entire architecture very well - Pugs, Parrot, Ponie, Perl6... any more?
But that was the dark side of lazyness, so I decided it was time to rise and see what has to be done. At the moment, I've been able to install it inside a user-space directory, which doesn't "clutter" the pseudo-production system I live in. I thought that it could be good to share this with you all, even if it's something that applies only here-and-now; just to take people lazier than me on the boat :)
My procedure in Linux (Slackware, so no rpm-s or similars):
Haskell is the first step. As of yesterday, version 6.4 is the latest available, so I link it here for your convenience. I appreciated the possibility to make in-place and avoid installing the package in a different place.
cd $HOME/src/ghc-6.4
./configure
make in-place
PATH="$PATH:$HOME/src/ghc-6.4/bin/i386-unknown-linux"
I actually added the last line to $HOME/.bashrc as well (I don't still plan to use it inside crontab jobs :)
Pugs README says that you need an additional library to do something that's obscure for me at the moment. But I wanted all whistles and bells, so I installed it as well:
cd $HOME/src/ghc-6.4/hs-plugins-20050501
./configure --prefix="$HOME/src/ghc-6.4/hs-plugins"
make
make install
make register
The last line is quite important, because it registers the library inside Haskell. I presume.
Time for Parrot now. For what I understood, it's the foundation floor for all the Perl 6 stuff, so I decided to install it before the other floors :)
perl Configure.pl --prefix="$HOME/sviluppo/parrot-0.2.0"
make
make test
# make install
Yes, last line is commented out. Which basically makes the prefix quite unuseful. Why? I don't know exactly, but it seems that Pugs feels more comfortable with the source tree of Parrot instead of the installed version - I had to fight with various errors in Pugs installation process before the light switched on. Good for me that I paid my dues to the local energy company.
export PUGS_EMBED=parrot
#export PARROT_PATH="$HOME/sviluppo/parrot-0.2.0"
export PARROT_PATH="$HOME/src/parrot-0.2.0"
These variables are needed for the following Pugs installation process. I decided to report all my installation process, so I report one more commented line, just to stress that the following Pugs installation process expects the path to the Parrot compilation directory instead of the installation one.
Pugs, at last! The previous setup (HS library, environment variables) gets rid of scary messages about being forced to do thing manually...
PUGSINSTALL="$HOME/sviluppo/pugs-6.2.3"
perl Makefile.PL PREFIX="$PUGSINSTALL" DESTDIR="$PUGSINSTALL"
make
make test
make install
PATH="$PATH:$PUGSINSTALL/bin"
Yes, I admit my ignorance, I really don't know the difference between PREFIX and DESTDIR, but without the latter the installation inside my home directory tree did not work :)
The whole process requires some compiling but should go quite smooth; in about 1 hour you'd have pugs at your fingertips and start playing with hangman (in
$HOME/src/Perl6-Pugs-6.2.3/examples/games), at last!
Flavio (perl -e 'print(scalar(reverse("\nti.xittelop\@oivalf")))')
Don't fool yourself.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
