Erick Tryzelaar wrote:
> Jonathan Kelly wrote:
>> but sometimes unexpected when you don't know! :)
>>
>> Hi,
>
> Hi again! It's fun having users :)
>>
>> I'm using svn from a few days ago (the current head build crashes).
>>
>
> First off, this comment. Did you use the most immediate version? If 
> it's still crashing, you may need to clean up everything by running 
> this (this assumes that you've already configured, and nothing in the 
> config changed):
>
> ./mk virgin (cleans as much as possible)
> ./interscript/bin/iscr.py lpsrc/flx_maker.pak (extract the build system)
> ./mk extract (extract all the .pak files)
> ./mk (build the source)
>
> If you're on a unix-like system, you can substitute those two "mk"s 
> with "make". If you're on windows, those would be "mk.bat".
>
> Anyway, is the build crashing, or reporting build errors? If it's 
> saying things like "test/stdlib/..." failed, that's known, and 
> ignorable. I've been extending our test framework, and felix hasn't 
> caught up yet. If it's doing something else, please let us know.
It wasn't getting to the tests. I had to start from scratch anyway 
because make was doing an "svn update" and I was getting an error about 
the current directory being from a different url. Anyway, now it builds 
and reports some test errors. Unfortunately, I blew away the old 
directory where I had the doco built, and now I can't rebuild the doco 
because it stops after errors in the tests. Hang on ... I just tried "mk 
doc" and that seems to be building, so that's cool.

<snip>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Felix-language mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/felix-language

Reply via email to