July 2015 - clasp-devel - mailman3.common-lisp.net

Trying to build demo-clasp-cxx on 0.3-test-8
by Chris Kohlhepp 22 Jul '15

22 Jul '15

Getting this compiler error: In file included from helloWorld.cc:5: In file included from /Applications/Clasp/clasp/src/include/clasp.h:1: In file included from /Applications/Clasp/clasp/include/clasp/core/../core/foundation.h:617: In file included from /Applications/Clasp/clasp/include/clasp/gctools/memoryManagement.h:117: /Applications/Clasp/clasp/include/clasp/gctools/pointer_tagging.h:217:21: error: unknown type name 'Fixnum' inline T tag_fixnum(Fixnum fn) { ^ /Applications/Clasp/clasp/include/clasp/gctools/pointer_tagging.h:218:37: error: use of undeclared identifier 'fixnum_shift' return reinterpret_cast<T>((fn << fixnum_shift)); ^ This was building fine under the master branch. Ideas? Regards Chris Kohlhepp

1 0

ASDF 3.1.5 released
by Robert Goldman 21 Jul '15

21 Jul '15

1 0

astmatcher-demo exposes major bugs in bclasp 0.3-test-7-8-g42f5e53
by Georgiy Tugai 10 Jul '15

10 Jul '15

I decided to test astmatcher-demo[1] (known to be working on f7948ae i.e. tip of master) on bclasp 0.3-test-7-8-g42f5e53 (tip of newbuild at the time). First, there is a missing external symbol NEW-DEDUPLICATING-REFACTORING-TOOL (called from src/lisp/clang-tool.lsp). I assumed that NEW-REFACTORING-TOOL would be a suitable replacement, evaluated the calling function definition (C-M-x in SLIME) and moved on. Then, a series of undefined symbols (see Table 1) followed, each one "fixed" by C-M-x. After this, astmatcher-demo's GET-CLASSES fails with "Bad keyword argument" followed by a large number (for example, 69993087673325; a decimal pointer address?) which was different between bclasp instances. On further investigation, it is interesting to note that LOADing clang-tool.lsp rather than REQUIREing 'clang-tool results in more undefined symbol errors (including the external symbol REPLACEMENTS-AS-LIST). I believe this is indicative of a significant difference between evaluation and compilation in bclasp. Table 1: clang-tool.lsp symbols misreported as undefined +----------------+--------------------------------------+ | DEFUN|IDENTIFY-HINT-ENVIRONMENT | |DEFINE-CONDITION|NODE-MATCHER-AMBIGUOUS-ERROR | | DEFUN|ERROR-UNLESS-VALID-PREDICATE | | DEFCONSTANT|+NODE-MATCHERS+ | | DEFUN|IDENTIFY-NODE-MATCHER-ENVIRONMENT | | DEFCONSTANT|+TRAVERSAL-MATCHERS+ | | DEFUN|IDENTIFY-TRAVERSAL-MATCHER-ENVIRONMENT| | DEFUN|APPLICABLE-MATCHER-P | | DEFUN|MATCH-RUN | +----------------+--------------------------------------+ References [1] https://github.com/drmeister/astmatcher-demo

1 2

Allosteric protein kinase inhibitors
by William Erbil 08 Jul '15

08 Jul '15

Dear Clasp developers, Has anyone thought about using Clasp in the development of protein kinase inhibitors that bind at protein-protein interfaces? Kaya

2 2

Another build error building 0.3-test-6
by Chris Kohlhepp 05 Jul '15

05 Jul '15

This error does not happen on a fresh checkout. Had previous master build and did a checkout of 0.3-test-6. Starting Clasp boehm-0.3 ... loading image... it takes a few seconds Building cleavir clasp full version - loading compile-cclasp.lisp Loading cleavir-system.lsp Loading/compiling source: #P"/Applications/Clasp/clasp/build/clasp/Contents/Resources/lisp/kernel/contrib/sicl/Code/Cleavir/Input-output/packages.lisp" Loading/compiling source: #P"/Applications/Clasp/clasp/build/clasp/Contents/Resources/lisp/kernel/contrib/sicl/Code/Cleavir/Input-output/io.lisp" Condition of type: SIMPLE-ERROR Noticed that the git command updating SICL contrib gives an error when not running a fresh checkout of 0.3-test-6. By the way, 0.3-test-5 builds fine. But I'm not sure what the benefits of 0.3-test-5 over master are. Best wishes Chris Kohlhepp

1 0

Build error building 0.3-test-6
by Chris Kohlhepp 05 Jul '15

05 Jul '15

Fresh checkout of 0.3-test-6 terminates with the following error: Linking epilogue-form Linking app-resources:lib;release;intrinsics_bitcode_boehm.o warning: Linking two modules of different target triples: /Applications/Clasp/clasp/build/clasp/Contents/Resources/lib/release/intrinsics_bitcode_boehm.o' is 'x86_64-apple-macosx10.7.0' whereas 'image' is 'x86_64-apple-macosx10.9.4' Running link time optimization module pass manager Generating object file /Applications/Clasp/clasp/build/clasp/Contents/Resources/lisp/build/system/cleavir-boehm/image.lbc --> /Applications/Clasp/clasp/build/clasp/Contents/Resources/lisp/build/system/cleavir-boehm/image.o reloc-model: RELOC-MODEL-DEFAULT make cclasp-boehm-asdf make[2]: *** No rule to make target `cclasp-boehm-asdf'. Stop. make[1]: *** [clasp-boehm] Error 2 make: *** [all] Error 2 I don't know if the target tripple difference between x86_64-apple-macosx10.7.0 and x86_64-apple-macosx10.9.4 is meaningful. I rather suspect no. Issue seems to be with ASDF. Predictably, we get an error trying to run the stock boehm target. ╭─chris@fergus /Applications/Clasp/clasp/build/clasp/MacOS ‹317b2e9*› ╰─➤ ./clasp_boehm_o Starting Boehm cclasp 0.3 ... loading image... it takes a few seconds Loading ASDF... Condition of type: SIMPLE-ERROR Module error: Don't know how to REQUIRE asdf. No restarts available. Top level. > (quit) My .clasprc contains a require asdf, by the way.

1 0