From: Christophe R. <cs...@ca...> - 2007-09-09 11:51:50
|
Aleksej Saushev <as...@ho...> writes: > The most recent version I've succeded to build is 1.0.6. > The system is NetBSD 4.99.31 i386, the current pkgsrc's SBCL > (which is 1.0.3) is known to be broken since spring, the reason > is similar to observed currently on 1.0.9. Any help is appreciated. > WARNING in RESTRICT-COMPILER-POLICY in lines 20..50 : > Unknown declaration POLICY-QUALITY. > The whole declaration will be ignored. > ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/compiler/policy.lisp-obj-tmp > 0 errors, 1 warning This is the first problem, I think; you could try removing the declaration in question -- (declare (policy-quality min)) in restrict-compiler-policy in src/compiler/policy.lisp -- or altering it to read (declare (type policy-quality min)). I'm not sure whether clisp is ignoring the compile-time effects of def!type, whether it is not allowing declarations of user-defined types to be used in their abbreviated form, or whether it has some separation of environments that we're not handling. > ** - Continuable Error > FAILURE-P was set when creating "obj/from-host/src/compiler/policy.lisp-obj". > Continue, using possibly bogus file "obj/from-host/src/compiler/policy.lisp-obj" In an ideal world, clisp would break into the debugger on the first error, and let you diagnose the problem yourself. Unfortunately, I have never worked out how to get it to do that (while still allowing noninteractive interaction on normal operation). For this and other reasons -- notably the non-repeatable build corruption that I have seen off and on for years using clisp -- I wouldn't recommend using it to bootstrap sbcls. I appreciate the theoretical purity for an OS distributor to be able to bootstrap sbcl without having a lisp compiler already, using clisp, but I think that if you want to do that you need to spend some time diagnosing clisp's particular intermittent difficulties with the sbcl build and genesis process. Best, Christophe |