Legend:
- Unmodified
- Added
- Removed
-
INSTALL
r20048 r20066 203 203 ---------------------------------------- 204 204 205 This note should describe a workaround to get the current pug snapshot running 206 under the following environment (I believe only the ghc stuff is essential for 205 This is only a way to get a running pugs with ghc 6.6.1 during the 206 migration phase to ghc 6.8.x. It *NOT* solves any issues. It is tested 207 with the following environment (I believe only the ghc part is essential for 207 208 this workaround): 208 209 … … 216 217 stm-2.0, template-haskell-2.1, time-1.1.1, unix-2.1 217 218 218 The last version that builds on this environment was revision 19955. 219 The last revision that builds directly from repository on this environment 220 was r19955. 219 221 220 222 1. Update to current version 221 ~/dev/pugs: svn up.223 svn update . 222 224 223 225 2. Revert some files to former version 224 ~/dev/pugs: svn up -r19955 src/Pugs/Meta/Str.hs src/Pugs/Types.hs src/UTF8.hs \ 225 Pugs.cabal.in util/build_pugs.pl third_party/ 226 227 3. Build it ... 228 ~/dev/pugs: perl Makefile.PL && make soon 229 230 4. ...twice 231 ~/dev/pugs: make soon 226 svn update -r19955 src/Pugs/Meta/Str.hs src/Pugs/Types.hs src/UTF8.hs \ 227 Pugs.cabal.in util/build_pugs.pl third_party/ \ 228 src/Pugs/Compile/Pugs.hs src/Pugs/Eval.hs 229 230 3. Build it ... 231 perl Makefile.PL && make 232 233 4. ..eventually twice, if it failed 234 make 232 235 233 236 5. Skip building Test.pm.yml 234 ~/dev/pugs:cp ext/Test/lib/Test.pm blib6/lib/235 236 Last two steps seems to be necessary to avoid messages like this237 cp ext/Test/lib/Test.pm blib6/lib/ 238 239 Last two steps seems sometimes to be necessary to avoid messages like this 237 240 ./pugs -CParse-YAML ext/Test/lib/Test.pm > blib6/lib/Test.pm.yml 238 241 pugs: user error (Not implemented: asYAML "Sub")
