From: Aleksej S. <as...@ho...> - 2007-09-09 10:53:56
|
Hello! 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. When running GNUMAKE=`which gmake` sh make.sh clisp I get the following messages (full log at request): /$scratchfilename=/tmp/canonicalize-whitespace-1.12969.tmp //entering make-host-1.sh //building cross-compiler, and doing first genesis i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8 Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2006 ;; Loading file src/cold/shared.lisp ... ;; Loading file src/cold/read-from-file.lisp ... ;; Loaded file src/cold/read-from-file.lisp ;; Loading file src/cold/rename-package-carefully.lisp ... ;; Loaded file src/cold/rename-package-carefully.lisp ;; Loading file src/cold/with-stuff.lisp ... ;; Loaded file src/cold/with-stuff.lisp ;; Loading file src/cold/ansify.lisp ... ;; Loaded file src/cold/ansify.lisp ;; Loading file src/cold/shebang.lisp ... ;; Loaded file src/cold/shebang.lisp target features *SHEBANG-FEATURES*= (:ANSI-CL :COMMON-LISP :SBCL :UNIX :SB-DOC :SB-TEST :SB-LDB :SB-PACKAGE-LOCKS :SB-UNICODE :SB-EVAL :SB-SOURCE-LOCATIONS :IEEE-FLOATING-POINT :X86 :BSD :NETBSD :ELF :GENCGC :STACK-GROWS-DOWNWARD-NOT-UPWARD :C-STACK-IS-CONTROL-STACK :COMPARE-AND-SWAP-VOP :UNWIND-TO-FRAME-AND-CALL-VOP :STACK-ALLOCATABLE-CLOSURES :ALIEN-CALLBACKS :LINKAGE-TABLE :OS-PROVIDES-DLOPEN :OS-PROVIDES-DLADDR :OS-PROVIDES-PUTWC :OS-PROVIDES-BLKSIZE-T) target backend-subfeatures *SHEBANG-BACKEND-FEATURES*=NIL ;; Loaded file src/cold/shared.lisp T ;; Loading file tools-for-build/ldso-stubs.lisp ... ;; Loaded file tools-for-build/ldso-stubs.lisp T #<PACKAGE SB-COLD> "obj/from-host/" ;; Loading file src/cold/set-up-cold-packages.lisp ... ;; Loaded file src/cold/set-up-cold-packages.lisp T ;; Loading file src/cold/defun-load-or-cload-xcompiler.lisp ... ;; Loaded file src/cold/defun-load-or-cload-xcompiler.lisp T Creating directory: /home/asau/tmp/sbcl-1.0.9/obj/from-host/ Creating directory: /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/ Creating directory: /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/ ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/show.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/show.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/show.lisp-obj ... ;; Loaded file obj/from-host/src/code/show.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/early-source-location.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/early-source-location.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/early-source-location.lisp-obj ... ;; Loaded file obj/from-host/src/code/early-source-location.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/backq.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/backq.lisp-obj-tmp The following functions were used but not defined: SB!INT:BUG 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/backq.lisp-obj ... ;; Loaded file obj/from-host/src/code/backq.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/defsetfs.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/defsetfs.lisp-obj ... ;; Loaded file obj/from-host/src/code/defsetfs.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cold-init-helper-macros.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cold-init-helper-macros.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/cold-init-helper-macros.lisp-obj ... ;; Loaded file obj/from-host/src/code/cold-init-helper-macros.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cross-misc.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cross-misc.lisp-obj-tmp The following functions were used but not defined: SB-XC:LDB SB-XC:DPB SB-XC:BYTE 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/cross-misc.lisp-obj ... ;; Loaded file obj/from-host/src/code/cross-misc.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cross-char.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cross-char.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/cross-char.lisp-obj ... ;; Loaded file obj/from-host/src/code/cross-char.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cross-byte.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cross-byte.lisp-obj-tmp The following functions were used but not defined: SB!INT:BUG 0 errors, 0 warnings ... ;; Loading file obj/from-host/src/code/cross-io.lisp-obj ... ;; Loaded file obj/from-host/src/code/cross-io.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp ... WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-8 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-16 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-32 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-64 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-SAP in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-WORD in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-SINGLE in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SAP-REF-DOUBLE in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SIGNED-SAP-REF-8 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SIGNED-SAP-REF-16 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SIGNED-SAP-REF-32 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SIGNED-SAP-REF-64 in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj WARNING: DEFSETF: redefining SETF-EXPANDER SIGNED-SAP-REF-WORD in /home/asau/tmp/sbcl-1.0.9/src/code/cross-sap.lisp, was defined in /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defsetfs.lisp-obj ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cross-sap.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/cross-sap.lisp-obj ... ;; Loaded file obj/from-host/src/code/cross-sap.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cross-thread.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cross-thread.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/cross-thread.lisp-obj ... ;; Loaded file obj/from-host/src/code/cross-thread.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cross-make-load-form.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cross-make-load-form.lisp-obj-tmp The following functions were used but not defined: SB!INT:BUG 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/cross-make-load-form.lisp-obj ... ;; Loaded file obj/from-host/src/code/cross-make-load-form.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/cross-condition.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/cross-condition.lisp-obj-tmp ... ;; Loading file obj/from-host/src/code/defbangtype.lisp-obj ... ;; Loaded file obj/from-host/src/code/defbangtype.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/defbangmacro.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defbangmacro.lisp-obj-tmp The following functions were used but not defined: SB!INT:MISSING-ARG SB!INT:SANE-PACKAGE 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/defbangmacro.lisp-obj ... ;; Loaded file obj/from-host/src/code/defbangmacro.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/defbangconstant.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defbangconstant.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/defbangconstant.lisp-obj ... ;; Loaded file obj/from-host/src/code/defbangconstant.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/primordial-extensions.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/primordial-extensions.lisp-obj-tmp The following functions were used but not defined: SB!INT:PARSE-BODY SB!C::LEXENV-BLOCKS 0 errors, 0 warnings ... ;; Loading file obj/from-host/src/code/early-array.lisp-obj ... ;; Loaded file obj/from-host/src/code/early-array.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/early-extensions.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/early-extensions.lisp-obj-tmp The following functions were used but not defined: SB!INT:PARSE-BODY SB!INT:STYLE-WARN 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/early-extensions.lisp-obj ... ;; Loaded file obj/from-host/src/code/early-extensions.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/parse-body.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/parse-body.lisp-obj-tmp The following functions were used but not defined: SB!INT:STYLE-WARN 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/parse-body.lisp-obj ... ;; Loaded file obj/from-host/src/code/parse-body.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/parse-defmacro.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/parse-defmacro.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/parse-defmacro.lisp-obj ... ;; Loaded file obj/from-host/src/code/parse-defmacro.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/compiler/deftype.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/compiler/deftype.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/compiler/deftype.lisp-obj ... ;; Loaded file obj/from-host/src/compiler/deftype.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/compiler/defconstant.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/compiler/defconstant.lisp-obj-tmp The following functions were used but not defined: SB!INT:STYLE-WARN SB!C::MAKE-DEFINITION-SOURCE-LOCATION SB!INT:INFO (SETF SB!KERNEL:FDOCUMENTATION) (SETF SB!INT:INFO) 0 errors, 0 warnings ... ;; Loading file obj/from-host/src/code/early-thread.lisp-obj ... ;; Loaded file obj/from-host/src/code/early-thread.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/defbangstruct.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/defbangstruct.lisp-obj-tmp The following functions were used but not defined: SB!KERNEL:LAYOUT-LENGTH SB!KERNEL:FIND-CLASSOID SB!KERNEL:CLASSOID-LAYOUT SB!KERNEL:LAYOUT-INFO SB!KERNEL:DD-SLOTS SB!KERNEL:DSD-ACCESSOR-NAME 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/defbangstruct.lisp-obj ... ;; Loaded file obj/from-host/src/code/defbangstruct.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/unportable-float.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/unportable-float.lisp-obj-tmp 0 errors, 0 warnings ;; Loading file obj/from-host/src/code/unportable-float.lisp-obj ... ;; Loaded file obj/from-host/src/code/unportable-float.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/code/type-class.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/code/type-class.lisp-obj-tmp The following functions were used but not defined: SB!KERNEL::HIERARCHICAL-UNION2 SB!KERNEL::HIERARCHICAL-INTERSECTION2 SB!KERNEL::TYPE-CLASS-INFO 0 errors, 0 warnings ... ;; Loading file obj/from-host/src/code/early-format.lisp-obj ... ;; Loaded file obj/from-host/src/code/early-format.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/compiler/early-c.lisp ... ;; Wrote file /home/asau/tmp/sbcl-1.0.9/obj/from-host/src/compiler/early-c.lisp-obj-tmp The following functions were used but not defined: SB!C::UNDEFINED-WARNING-NAME SB!C::UNDEFINED-WARNING-KIND SB!INT:STYLE-WARN 0 errors, 0 warnings ;; Loading file obj/from-host/src/compiler/early-c.lisp-obj ... ;; Loaded file obj/from-host/src/compiler/early-c.lisp-obj ;; Compiling file /home/asau/tmp/sbcl-1.0.9/src/compiler/policy.lisp ... 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 ** - 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" ;; Loading file tests/type.before-xc.lisp ... ** - Continuable Error EVAL: undefined function TYPE= Continue, using possibly bogus file "obj/from-host/src/compiler/policy.lisp-obj" ;; Loading file tools-for-build/ucd.lisp ... ;; Loaded file tools-for-build/ucd.lisp T 181 304 305 383 453 456 459 498 837 962 976 977 981 982 1008 1009 1012 1013 7835 8126 8486 8490 8491 7897 ** - Continuable Error EVAL: undefined function HOST-CLOAD-STEM Continue, using possibly bogus file "obj/from-host/src/compiler/policy.lisp-obj" ** - Continuable Error EVAL: undefined function SB!VM:GENESIS Continue, using possibly bogus file "obj/from-host/src/compiler/policy.lisp-obj" deleted #P"/home/asau/tmp/sbcl-1.0.9/obj/from-host/src/compiler/policy.lisp-obj-tmp" Bye. 7.97 real 5.79 user 1.49 sys //entering make-target-1.sh //building runtime system and symbol table file gmake: Entering directory `/home/asau/tmp/sbcl-1.0.9/src/runtime' GNUmakefile:31: genesis/Makefile.features: No such file or directory gmake: *** No rule to make target `genesis/Makefile.features'. Stop. gmake: Leaving directory `/home/asau/tmp/sbcl-1.0.9/src/runtime' 0.02 real 0.00 user 0.01 sys |
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 |
From: Christophe R. <cs...@ca...> - 2007-09-14 14:08:59
|
Aleksej Saushev <as...@ho...> writes: > Thanks for the hint, I'll suggest the patch (see attachment) to > pkgsrc maintainers. With this patch I'm successful to build SBCL > 1.0.8 under pkgsrc framework (that is: update version number, > add patch, "make distinfo", "make"). > > For 1.0.9 I get fail with attached log. Any suggestions? Build with a lisp that is not CLISP. (This is precisely the kind of non-repeatable build corruption that I referred to in my last message -- non-repeatable in that trivial changes make the problem go away.) >> 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. > > There's no other portable (and free!) Common Lisp implementation > to use for bootstrapping, CLISP just works. Sometimes. > >> 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. > > pkgsrc is very nice framework, it's stable and works in any sane > environment. And I don't see the reason, why anyone needing, say, > Maxima, should fight installation of SBCL, which should be done in > rather unconvenient way. Is it not the case that pkgsrc could use binary versions of SBCL to build SBCL, rather than depending on whatever random clisp version is currently in the system? How does gcc get bootstrapped? Cheers, Christophe |
From: Aleksej S. <as...@ho...> - 2007-09-14 23:25:16
|
Christophe Rhodes <cs...@ca...> writes: > Aleksej Saushev <as...@ho...> writes: > >> Thanks for the hint, I'll suggest the patch (see attachment) to >> pkgsrc maintainers. With this patch I'm successful to build SBCL >> 1.0.8 under pkgsrc framework (that is: update version number, >> add patch, "make distinfo", "make"). >> >> For 1.0.9 I get fail with attached log. Any suggestions? > > Build with a lisp that is not CLISP. (This is precisely the kind of > non-repeatable build corruption that I referred to in my last message > -- non-repeatable in that trivial changes make the problem go away.) There's no other Common Lisp implementaion. Can you suggest specific one, which could be compiled within usual UNIX and alike framework? >>> 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. >> >> There's no other portable (and free!) Common Lisp implementation >> to use for bootstrapping, CLISP just works. Sometimes. >> >>> 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. >> >> pkgsrc is very nice framework, it's stable and works in any sane >> environment. And I don't see the reason, why anyone needing, say, >> Maxima, should fight installation of SBCL, which should be done in >> rather unconvenient way. > > Is it not the case that pkgsrc could use binary versions of SBCL to > build SBCL, rather than depending on whatever random clisp version is > currently in the system? How does gcc get bootstrapped? GCC is not bootstrapped, you can have no GCC at all, and pkgsrc specifically supports native C compilers, where it is appropriate. |
From: Christophe R. <cs...@ca...> - 2007-09-14 23:44:18
|
Aleksej Saushev <as...@ho...> writes: > Christophe Rhodes <cs...@ca...> writes: > >> Build with a lisp that is not CLISP. (This is precisely the kind of >> non-repeatable build corruption that I referred to in my last message >> -- non-repeatable in that trivial changes make the problem go away.) > > There's no other Common Lisp implementaion. > Can you suggest specific one, which could be compiled within usual > UNIX and alike framework? No. (Well, that depends slightly on whether Java counts as being within a usual UNIX and alike, but "no" is probably the simplest answer.) The alternative to building with a lisp that is not CLISP is to do some work to debug the CLISP build failures; a first step would be to eliminate all things that can vary between builds: records of pathnames, timestamps and the like, and then do a byte-for-byte comparison of cross-compiler fasl files between say CLISP and SBCL. That would be worthy work, but is clearly some effort -- but maybe less effort for you than to use something other than CLISP, I don't know. If you're interested in doing some of this work, I can provide a starting point. Cheers, Christophe |
From: Juho S. <js...@ik...> - 2007-09-15 16:55:43
|
Aleksej Saushev <as...@ho...> writes: > Christophe Rhodes <cs...@ca...> writes: > > The alternative to building with a lisp that is not CLISP is to do > > some work to debug the CLISP build failures; a first step would be to > > eliminate all things that can vary between builds: records of > > pathnames, timestamps and the like, and then do a byte-for-byte > > comparison of cross-compiler fasl files between say CLISP and SBCL. > > That would be worthy work, but is clearly some effort -- but maybe > > less effort for you than to use something other than CLISP, I don't > > know. If you're interested in doing some of this work, I can provide > > a starting point. > > Alright. I see no other way currently. > Should I contact CLISP developers? Probably not, unless you can give them a significantly smaller test case exhibiting the bug than all >200kloc of sbcl, with an error occuring at some unknown point during a 10 minute build process. (Note that it's not certain that the problem is in CLisp; it's also possible that there's some bug in the sbcl, which isn't triggered the other implementations that are able to build sbcl). The suggestions Christophe made involve changing the sbcl cross-compiler, not CLisp. It's unfortunately not just a matter of getting rid of timestamps etc. I think stuff like pretty-printed sexps can also end up in fasls. -- Juho Snellman |
From: Christophe R. <cs...@ca...> - 2007-09-15 17:12:44
|
Juho Snellman <js...@ik...> writes: > I think stuff like pretty-printed sexps can also end up in fasls. Oh really? Then I'm actually much more liable to suspect stuff like pretty-printed sexps (from CLISP), as the pretty printer is responsible for gc crashes in CLISP (see the inhibit-warnings policy declaration in make-host-2.lisp). That is, if there is a difference in pretty printing, that might in itself be the cause of a problem. Anyway, timestamps would be where I would start (including in the debug information.) Cheers, Christophe |
From: Aleksej S. <as...@ho...> - 2007-09-15 15:55:05
|
Christophe Rhodes <cs...@ca...> writes: >> There's no other Common Lisp implementaion. >> Can you suggest specific one, which could be compiled within usual >> UNIX and alike framework? > > No. (Well, that depends slightly on whether Java counts as being > within a usual UNIX and alike, but "no" is probably the simplest > answer.) Well, Java is no better. > The alternative to building with a lisp that is not CLISP is to do > some work to debug the CLISP build failures; a first step would be to > eliminate all things that can vary between builds: records of > pathnames, timestamps and the like, and then do a byte-for-byte > comparison of cross-compiler fasl files between say CLISP and SBCL. > That would be worthy work, but is clearly some effort -- but maybe > less effort for you than to use something other than CLISP, I don't > know. If you're interested in doing some of this work, I can provide > a starting point. Alright. I see no other way currently. Should I contact CLISP developers? |
From: NIIMI S. <sa...@sa...> - 2007-09-15 17:23:22
|
Aleksej Saushev wrote: > Alright. I see no other way currently. Why not to use SBCL binaries to bootstrap SBCL? If the target system is supported by SBCL, bootstrapping binaries can be prepared. I use such method on FreeBSD's port lang/sbcl. -- NIIMI Satoshi |