ecl-devel October 2017

ecl-devel@common-lisp.net

6 participants
4 discussions

16.1.3 mingw-w64-x86_64 build error
by Dave Richards 02 Nov '17

02 Nov '17

I ran configure and only provided the --prefix argument. The 32-bit build worked fine, but the 64-bit build failed, see below. Dave cd build; make make[1]: Entering directory '/c/Dave/ecl-16.1.3/build' Building libeclmin.a... Building ecl_min.exe... ;*** Lisp core booted **** ECL (Embeddable Common Lisp) ;;; ;;; Welcome to bare.lsp. Let's bring this instance up! ;;; ;;; ;;; About to load lsp/load.lsp ;;; ;;; Loading src:lsp;export.lsp ;;; Unhandled lisp initialization error ;;; Message: FILE-ERROR ;;; Arguments: (:PATHNAME #P"SRC:LSP;EXPORT.LSP.NEWEST") Internal or unrecoverable error in: Lisp initialization error. This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. make[1]: *** [Makefile:241: bin/ecl.exe] Error 3 make[1]: Leaving directory '/c/Dave/ecl-16.1.3/build' make: *** [Makefile:72: all] Error 2

2 2

ECL and musl
by Lucas Ramage 20 Oct '17

20 Oct '17

Hello, I am attempting to package ecl for alpine linux and I am having troubles compiling against musl. Building ecl_min... .//libeclgc.a(mach_dep.o): In function `GC_with_callee_saves_pushed': /root/ecl-16.1.3/src/bdwgc/mach_dep.c:245: undefined reference to `getcontext' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:224: ecl_min] Error 1 make[1]: Leaving directory '/root/ecl-16.1.3/build' make: *** [Makefile:72: all] Error 2 I tried `make CFLAGS='-DNO_GETCONTEXT'` but that did not work either. Has anyone successfully built ecl using musl? -- Regards, [image: Visit online journal] <https://lramage94.github.io/> *Lucas Ramage* / Software Engineer ramage.lucas(a)openmailbox.org / (941) 404-6794 *PGP Fingerprint* / Learn More <https://emailselfdefense.fsf.org/en/> EAE7 45DF 818D 4948 DDA7 0F44 F52A 5A96 7B9B 6FB7 <https://pgp.mit.edu/pks/lookup?op=get&search=0xF52A5A967B9B6FB7> *Visit online journal* http://lramage94.github.io <https://lramage94.github.io/> [image: Github] <https://github.com/lramage94>[image: Linkedin] <https://www.linkedin.com/in/lramage94>

3 3

ASDF 3.3 is released
by Robert Goldman 07 Oct '17

07 Oct '17

Today we release ASDF 3.3. The most substantial change is to the build planning process, which has been reformed by François-René Rideau so that DEFSYSTEM-DEPENDS-ON now behaves correctly. There are a number of other improvements, and we are indebted to Daniel Kochmanski, Rommel Martinez, and Chun Tian for contributions. Thanks again to Anton Vodonosov and Dave Cooper for support in testing, and new thanks to Martti Halminen, Jens K. Loewe, and Jason Miller. I would like to dedicate this ASDF release to the late Elias Pipping. On a technical level, Elias made great improvements in some of the most challenging ASDF internals, notably the RUN-PROGRAM component of UIOP, a place where implementations are not constrained by the language specification, diverge radically from each other, and are poorly documented. On a personal level, Elias was very supportive to me as ASDF maintainer, and while I was going through an illness. He did all these things despite being gravely ill with the cancer that eventually killed him. He will be greatly missed, Z'chrono L'vracha. We urge implementations that are currently bundling previous versions of ASDF to adopt 3.3.0 at their earliest convenience. The improvements offered in this release will substantially improved the reliability and predictability of ASDF use. Details on bugfixes can be found at https://launchpad.net/asdf and in the discussions in merged branches of https://gitlab.common-lisp.net/asdf/asdf Here is the changelog entry for 3.3: cl-asdf (2:3.3.0-1) unstable; urgency=low New milestone: * Build-plan: Extensively revised the build plan process so that :DEFSYSTEM-DEPENDS-ON would work correctly, even when depended on systems change (which didn't work before). See our ELS demonstration about it: "Delivering Common Lisp Applications with ASDF 3.3" < https://github.com/fare/asdf2017 > * Internals: to support the above, many ASDF internals have changed. ASDF now has the notion of multiple build phases to a common build session (which generalizes the previous build cache). ASDF considers loading a .asd file as an operation DEFINE-OP, and tracks as dependencies files mentioned during in :LOAD-FILE-FORM statements, etc. Some code has moved to new files or among old files, and between packages. Actions are now uniformly represented as a CONS of an OPERATION and a COMPONENT, where in some cases previously only the class of the operation was preserved. Forcing is constrained to be uniform across all phases of a top level ASDF operation invocation. Fixed the protocol for resetting systems being (re)defined, allowing subclasses to define default slot values. Remove *LOAD-SYSTEM-OPERATION*, as the current maintainer of ECL, for which it was originally designed, decided that it could never be made to work properly, after all. * ASDF&UIOP: Tweak dependencies between ASDF and UIOP. To avoid DEFINE-OP circularity, asdf.asd with no longer causes uiop.asd to be loaded. A standalone UIOP won't be loaded at all unless it's strictly more recent than ASDF. * Tests: tests for new capabilities and bugs. Test backtraces can be disabled. * Documentation: a number of improvements and clarifications. * Feature: a new feature :asdf3.3 * ECL: restored the deprecated function MAKE-BUILD, removed in 3.2.0, in a way that works on top of supported APIs (we still recommend you migrate to these supported APIs). Also stop using the deprecated COMPUTE-INIT-NAME. * Deprecation: starting to emit STYLE-WARNINGs for deprecated functions. Will gradually escalate to true WARNINGs and then ERRORs. -- Robert P. Goldman <rpgoldman(a)sift.net> Sun, 20 August 2017 21:00:00 -0500 Robert P. Goldman Research Fellow Smart Information Flow Technologies (d/b/a SIFT, LLC) 319 N. First Ave., Suite 400 Minneapolis, MN 55401 Voice: (612) 326-3934 Email: rpgoldman(a)SIFT.net

1 0

Help.doc loading in Binary
by John Mercouris 06 Oct '17

06 Oct '17

Hello everyone, I’m running ECL + EQL 16.1.3, Mac OS High Sierra I can produce a binary with ECL, but I have an issue, when I try to run it on anybody’s computer: I get the following: ------------------------------------------------------ Condition of type: FILE-ERROR Filesystem error with pathname “SYS:help.doc”. Either 1) the file does not exist, or 2) we are not allowed to access the file, or 3) the pathname points to a broken symbolic link. No restarts available. Top level in: #<process TOP-LEVEL>. > ------------------------------------------------------ I’ve determined that the cause of this error is a file missing at: /usr/local/lib/ecl-16.1.3/help.doc I’ve been able to get binary files to work on other people’s machines by copying the help.doc file to the appropriate dir. Unfortunately this is not a practical solution for distribution. Is there any way to tell ECL to not attempt to load this file? Any patch I can apply to the source? Thanks, -John

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

ecl-devel October 2017