On Mar 30, 2009, at 9:24 AM, Emmanuel Onzon wrote:

> Anyhow the big problem is labour.
>
> Ok.
> Maybe I can help to do this update, I have to see.
> But I fail to build the compiler (r2396):
>
> when doing 'make config' I get :
> make: *** Pas de règle pour fabriquer la cible « config/init__.py »,  
> nécessaire pour « config ». Arrêt.
>
> when doing ./configure I get :
>
> Interscript 1.0a11[117] Process Mon 30 Mar, 2009 18:19:55 (CEST)
> PROCESSING WHOLE FILE (options changed)
> $Id: flx_maker.pak 2217 2008-08-19 09:39:25Z skaller $
> Pass 1 status: <not converged>
>   Files    : 30
>   New      : 19
>   Changed  : 6
>   Unchanged: 5
> Elapsed Process Time 0 seconds
>
> after about 4 minutes.


I've started updating dypgen to the latest released version, and I'm  
running into a couple problems. First off, it looks like dypgen now  
generates and compiles a temporary file, and is erroring out:

 > build/src/compiler/dyp/dypgen/dypgen --ocamlc "-I build/src/ 
compiler/dyp/dyplib -I build/src/compiler/sex" build/src/compiler/sex/ 
sex_parse.dyp
File "build/src/compiler/sex/sex_parse.temp.ml", line 1, characters 0-1:
Warning X: bad source file name: "Sex_parse.temp" is not a valid  
module name.
File "build/src/compiler/sex/sex_parse.dyp", line 1, characters 8-22:
Error: Unbound module Sex_token

I'm not sure if we can do anything about the warning, but the error is  
happening because my build system can't determine that build/src/ 
compiler/sex/sex_parse.dyp depends on build/src/compiler/sex/ 
sex_token.mli and build/src/compiler/sex/sex_types.mli, and doesn't  
know that it needs to compile the .cmi file first. After manually  
creating it, I'm running into this:

 > build/src/compiler/dyp/dypgen/dypgen --pv-obj --noemit-token-type -- 
ocamlc -I build/src/compiler/dyp/dyplib -I build/src/compiler/flx_lex  
build/src/compiler/flx_lex/flx_preparse.dyp
File "build/src/compiler/flx_lex/flx_preparse.dyp", from l:103, c:0 to  
l:104, c:0 :
Lexing failed with message: lexing: empty token

Oh, and I see that dypgen dropped support for the '--prio-pt' flag. I  
have to admit I'm not sure what does that flag mean. The CHANGES file  
mentioned that there are alternative ways of getting that  
functionality. So is that related to the error and what do I have to  
do about it?

Thanks for the help.
------------------------------------------------------------------------------
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language

Reply via email to