| Allegro CL version 8.2 Unrevised from 8.1 to 8.2. 8.1 version |
This is the class of condition signaled when an attempt is made to load an incompatible fasl file into a running Lisp. This can happen in two ways:
The internal fasl version number is stored in the fasl file but not in a way that can be read by humans. If you want to find out in gross terms if your file foo.fasl is compatibe with your lisp, type head -4 foo.fasl into most UNIX shells, or into cygwin on Windows (some versions of head might require a different style of specifying only 4 lines). The first 4 lines of the fasl file are (mostly) human readable starting with "<AcL>" (if such a string doesn't appear on the first line, then it is likely either a corrupted file or a fasl generated by another Lisp implementation).
The second line will contain the string identifying the lisp which compiled it. It will include a Lisp version, an architecture, and a date. If the first two items don't match what startup information is printed on your Lisp, then it is the likely cause of the error.
file-incompatible-fasl-error
condition
cannot be counted on to distinguish different Lisps. However this
error will be generated whenever an attempt is made to load a Windows
fasl file into a non-Windows Lisp, or to load a non-Windows fasl file
into a Windows Lisp.
This is not the error signaled when trying to load a fasl file generated on one architecture into a Lisp running on another architecture.
See errors.htm for general information on errors in Allegro CL.
Copyright (c) 1998-2016, Franz Inc. Oakland, CA., USA. All rights reserved.
This page was not revised from the 8.1 page.
Created 2010.1.21.
| Allegro CL version 8.2 Unrevised from 8.1 to 8.2. 8.1 version |