Thanks, that did the trick. Sweet! How do I make yi look in the source tree instead of the install directory for its modules? Well, I could soft-link I guess.
Also, I got the impression that the Gtk interface is unreliable at the moment? Is that right? If so, I'll have a go at that. cheers, Fraser. One more thing -- when I run ./dist/build/yi/yi it's not finding any of the modules (e.g. Yi.Prelude). I thought that might be because it's looking in ~/.yi, but softlinking ~/.yi/Yi to ~/usr/src/yi/Yi didn't help. I guess there's a way to set the search path for imported modules, but clearly it's not in yi.hs. Is it bette On Thu, Feb 26, 2009 at 10:19 PM, Jean-Philippe Bernardy < [email protected]> wrote: > > On Thu, Feb 26, 2009 at 6:02 PM, Fraser Wilson <[email protected]> > wrote: > > Hi all, > > > > I've just run darcs get on my yi repository. After a runhaskell Setup > > configure, should I expect that alex has been run on the .x files in > > Yi/Lexer? Or should this happen during the build? > > This happens in the build. > > > In any case, I tried to work around this like so: > > > > cd Yi/Lexer ; for i in *.x; do echo $i; alex $i; done > > > > Which got the build running again, but then stopped here: > > > > [10 of 17] Compiling Yi.Lexer.Haskell ( Yi/Lexer/Haskell.hs, > > dist/build/parserTest/parserTest-tmp/Yi/Lexer/Haskell.o ) > > > > Yi/Lexer/alex.hsinc:26:17: Parse error in pattern > > > > and I'm not sure where to go from here. Am I missing something? > > I think we screwed up something the parserTest executable description. > As a workaround, try to remove the parserTest executable description > from yi.cabal. > > Cheers, > JP. > > > > -- http://thewhitelion.org/mysister --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
