Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


#<SB-SYS:FD-STREAM for "file /var/tmp/clbuild.paktahn/source/trivial-features/src/tf-sbcl.fasl" {1003110491}> was compiled for implementation X86, but this is a X86-64 #1

gour opened this Issue · 2 comments

2 participants

Gour Leslie P. Polzer


Here is the result of attempting to build latest snapshot:

[gour@gaura-nitai paktahn] makepkg -f
==> Making package: paktahn 0.8-1 x86_64 (Wed Aug 12 16:29:39 CEST 2009)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Found paktahn-0.8.tar.bz2 in build dir
==> Validating source files with md5sums...
paktahn-0.8.tar.bz2 ... Passed
==> Extracting Sources...
-> bsdtar -x -f "paktahn-0.8.tar.bz2"
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting build()...
; loading system definition from /usr/lib/sbcl/sb-grovel/sb-grovel.asd into
; #
; registering # as SB-GROVEL
; loading system definition from
; /var/tmp/clbuild.paktahn/systems/trivial-features.asd into #
; registering # as TRIVIAL-FEATURES

debugger invoked on a SB-FASL::INVALID-FASL-IMPLEMENTATION in thread #:
# was compiled for implementation X86, but this is a X86-64.

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
0: [TRY-RECOMPILING] Recompile tf-sbcl and try loading it again
1: [RETRY ] Retry performing # on
2: [ACCEPT ] Continue, treating # on
# as having been
3: [CONTINUE ] Ignore runtime option --load "main.lisp".
4: [ABORT ] Skip rest of --eval and --load options.
5: Skip to toplevel READ/EVAL/PRINT loop.
6: [QUIT ] Quit SBCL (calling #'QUIT, killing the process).


It looks as pretty simpe to fix for you. ;)


Leslie P. Polzer

Just delete all .fasl files from the dependency tree. I'm going to upload the tarball without them in addition.


Thanks. It was required to rm some libs as well.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.