Changeset 8941
- Timestamp:
- 02/02/06 18:09:14 (3 years ago)
- Files:
-
- 3 modified
Legend:
- Unmodified
- Added
- Removed
-
INSTALL
r8922 r8941 56 56 export PUGS_EMBED="perl5 parrot" (bash) 57 57 setenv PUGS_EMBED "perl5 parrot" (csh) 58 59 XXX Note!60 Using embedded parrot is currently NOT recommended on win32 and x86_64.61 58 62 59 To build with an embedded parrot interpreter, make sure the PUGS_EMBED -
Makefile.PL
r8933 r8941 378 378 environment variable to contain 'parrot', the PARROT_PATH environment 379 379 variable to the path of a built parrot tree, then run Makefile.PL again. 380 Linking against Parrot is currently NOT recommended on win32 and x86_64.381 380 382 381 . -
TASKS
r8940 r8941 34 34 check if parrot is there with can_run('parrot'). Skills: basic perl5. 35 35 36 * Remove the "embedding parrot is NOT recommended on" lines from37 Makefile.PL and INSTALL. They were just there for the 6.2.11 release.38 Skills: none.39 40 36 * docs/notes contains context_coercion.pod (audreyt's) and 41 37 context_coersion.pod [sic] (luqui's). Name (one of?) them something 42 38 more reasonable. Skills: taste. 43 39 44 * ./pugs -V doesn't mention a lot of stuff. Notably, whether parrot 45 and or p6 have been embedded. It should. May be hard? - the build 46 system is a bit messy. It should perhaps also answer the "usual 47 questions for someone with a problem" - what os, cpu (64 bit?), ghc 48 version, gcc version. But that could be a separate task. Skills: p5, 49 build system. 40 * ./pugs -V doesn't mention / is sloppy about a lot of stuff: 41 Skills: p5, build system. 42 ** Notably, whether parrot and or p6 have been embedded. It should. 43 May be hard? - the build system is a bit messy. 44 ** It should perhaps also answer the "usual questions for someone with 45 a problem" - what os, cpu (64 bit?), ghc version, gcc version. 46 ** Some of the data lifted from `perl -V` at build time is bogus; for 47 example, `archname` on my system is i486-linux-gnu-thread-multi 48 because that's where debian's perl came from.
