- Jan 22, 2009
-
-
rtoy authored
bootstrap file.)
-
- Sep 17, 2008
-
-
rtoy authored
everywhere. This makes the cross-compile scripts look much more similiar and might allow us to extract the common bits out.
-
- May 24, 2008
-
-
rtoy authored
o Clean up list of features. This file should now actually work for all x86 builds.
-
- Feb 06, 2008
-
-
rtoy authored
-
- Feb 05, 2008
-
-
rtoy authored
OLD-SPARC:SIMPLE-ARRAY-DOUBLE-DOUBLE-FLOAT-TYPE. Removes a few warnings/issues during cross-compile. o Update EXTERN-ALIEN-NAME to match the actual definition. No supported x86 system needs anything special. (The previous version was causing failures on x86/darwin.)
-
- Jan 30, 2008
-
-
rtoy authored
-
- Aug 11, 2006
-
-
rtoy authored
support, and update *features* to :cmu19c instead of :cmu19a.
-
- Jan 12, 2004
-
-
toy authored
o Add some comments.
-
- Oct 17, 2003
-
-
toy authored
his 2.4 release).
-
- Aug 27, 2002
-
-
moore authored
On x86 FreeBSD and Linux, change the way foreign symbol addresses are resolved. They now go through a table -- effectively a new space in the core file. Function references are resolved lazily, data references are resolved on startup and when a .so is loaded. The end result is that cores can be dumped that contain references to symbols in shared libraries. Also, the dependence of the core on addresses in the Lisp runtime is broken. The linkage table feature is controlled by :linkage-table and LINKAGE_TABLE in C runtime. Several foreign symbols are now Lisp static symbols, so a cross compile is required whether or not the new stuff is used. I've checked in boot4-cross-foreign-linkage.lisp that builds the compiler for linkage table; do whatever you usually do for the non-linkage table case:) Seriously, lets start a discussion on standardizing "cross compilation," not to mention the general build procedure.
-