sbcl Log

Commit Date  
[267724] (1.5 kB) by Nikodemus Siivola Nikodemus Siivola fix build with clisp 2.49

Patch by Josh Elsasser, lp#629144.

Previously, if a clisp 2.49 host was used, the build failed during
make-host-1 in src/code/cross-sap.lisp with several "redefining SETF
expander" errors. The same *suppress-check-redefinition* fix used in
make-host-2 is enough to placate clisp and allow the build to finish

2010-09-03 13:28:34 View
[577487] (1.4 kB) by Alastair Bridgewater Alastair Bridgewater Build system refactoring

Moved flag processing as far "inward" as possible when dealing with
compile-stem, reducing the amount of redundant code for parsing out and
passing along boolean keywords based on the presence or absence of a
flag and eliminating some of the keyword arguments to compile-stem.

Added a "mode" parameter to compile-stem to enable determining the
correct compile-file function based on the combination of mode and
flags, further simplifying the interface.

Added new functions for determining the source and object pathnames
for a stem, fixing a longstanding KLUDGE in host-load-stem,
consolidating the three instances of code to compute an object pathname
and the two instances of code to compute a source pathname and
eliminating the rest of the keyword arguments to compile-stem.

2009-05-05 17:10:29 View
[77bf76] (1.4 kB) by Christophe Rhodes Christophe Rhodes Fewer XC/reader-conditional confusions
Inspired by Josh Elasser (sbcl-devel 2008-08-29), write code
that tries to be clever about reader conditionals in the
cross-compiler, in order to point out when a mistake is likely.
... and fix the extra buglet that this reveals.

2008-09-04 13:04:45 View
[89987c] (1.3 kB) by Christophe Rhodes Christophe Rhodes
Beginnings of a Win32 merge.
... rearrange the build scripts to use input from files rather
than <<HERE documents.
... (no other changes; just working to get the meaty changes
isolated from the fluff)

2005-12-29 16:08:31 View

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks