X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=93066ab4c4cb331a526cf420891f26879157c2c1;hb=7d853ed1882221bc790062e423a74a620f6e4ee1;hp=6e8a691b66b3df82a5b388afb77d1df0a208395c;hpb=a4882e3023fdd5e777169a4cbede33605281173c;p=sbcl.git diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index 6e8a691..93066ab 100644 --- a/base-target-features.lisp-expr +++ b/base-target-features.lisp-expr @@ -7,10 +7,13 @@ ;;;; ;;;; Note that the recommended way to customize the features of a ;;;; local build of SBCL is not to edit this file, but instead to -;;;; tweak customize-target-features.lisp. If you define a function -;;;; in customize-target-features.lisp, it will be used to transform -;;;; the target features list after it's read and before it's used. -;;;; E.g. you can use code like this: +;;;; tweak customize-target-features.lisp. (You must create this file +;;;; first; it is not in the SBCL distribution, and is in fact +;;;; explicitly excluded from the distribution in places like +;;;; .cvsignore.) If you define a function in +;;;; customize-target-features.lisp, it will be used to transform the +;;;; target features list after it's read and before it's used. E.g., +;;;; you can use code like this: ;;;; (lambda (list) ;;;; (flet ((enable (x) (pushnew x list)) ;;;; (disable (x) (setf list (remove x list)))) @@ -191,6 +194,11 @@ ;; character set. :sb-unicode + ;; Support for a full evaluator that can execute all the CL special + ;; forms, as opposed to the traditional SBCL evaluator which called + ;; COMPILE for everything complicated. + :sb-eval + ;; Record source location information for variables, classes, conditions, ;; packages, etc. Gives much better information on M-. in Slime, but ;; increases core size by about 100kB. @@ -226,6 +234,16 @@ ;; again, if anyone's sufficiently motivated. ; :long-float + ;; Some platforms don't use a 32-bit off_t by default, and thus can't + ;; handle files larger than 2GB. This feature will control whether + ;; we'll try to use platform-specific compilation options to enable a + ;; 64-bit off_t. The intent is for this feature to be automatically + ;; enabled by make-config.sh on platforms where it's needed and known + ;; to work, you shouldn't be enabling it manually. You might however + ;; want to disable it, if you need to pass file descriptors to + ;; foreign code that uses a 32-bit off_t. + ; :largefile + ;; ;; miscellaneous notes on other things which could have special significance ;; in the *FEATURES* list