ecl-devel February 2020

ecl-devel@common-lisp.net

6 participants
5 discussions

Is this thing on? Cross-compiling for ARM
by Erik Winkels 26 Sep '20

26 Sep '20

Hi all, Not sure if this is still the place to be for ECL questions but here it goes: I'm having issues cross-compiling ECL for ARM and since this is actually the first time I'm cross-compiling stuff ever I'm kinda stuck. I want to cross-compile for ARM, *but* it is not for Android it is for Sailfish OS. There's an (unofficial) ECL package available for it but I cannot find a way to contact the author and also don't want to depend on it. On my Void Linux machine I've installed `cross-arm-linux-gnueabi` and can do a `./configure --host=arm-linux-gnueabi` but when I do `make` I get the following errors: ``` dpp: /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d -> list.o.c Unknown symbol: mp::compare-and-swap-car Unknown symbol: mp::atomic-incf-car Unknown symbol: mp::compare-and-swap-cdr Unknown symbol: mp::atomic-incf-cdr /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_compare_and_swap_car': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:670:26: error: 'unknown' undeclared (first use in this function) return ecl_compare_and_swap(&ECL_CONS_CAR(x), old, new); ^~~~~~~ /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:670:26: note: each undeclared identifier is reported only once for each function it appears in /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_atomic_incf_car': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:678:26: error: 'unknown' undeclared (first use in this function) return ecl_atomic_incf(&ECL_CONS_CAR(x), increment); ^~~~~~~ /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_compare_and_swap_cdr': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:686:26: error: 'unknown' undeclared (first use in this function) return ecl_compare_and_swap(&ECL_CONS_CDR(x), old, new); ^~~~~~~ /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_atomic_incf_cdr': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:694:26: error: 'unknown' undeclared (first use in this function) return ecl_atomic_incf(&ECL_CONS_CDR(x), increment); ^~~~~~~ make[2]: *** [Makefile:88: list.o] Error 1 make[2]: Leaving directory '/home/brainrot/projects/eclrepl/3rd-party/ecl-git/build/c' make[1]: *** [Makefile:144: libeclmin.a] Error 2 make[1]: Leaving directory '/home/brainrot/projects/eclrepl/3rd-party/ecl-git/build' make: *** [Makefile:72: all] Error 2 ``` I get the feeling I'm forgetting some necessary steps. Thanks, Erik

4 19

ASDF problem on second load of ECL
by querent 27 Feb '20

27 Feb '20

Hi there, I am just trying to use ECL for a little project of mine, but I have a problem. Immediately after installation, things seem to work fine. I can run things, produce executables, etc. However, the second time I load ECL I get the error listed below. Deleting .cache/common-lisp/ecl-16.1.3 removes the error, but of course the world gets recompiled every time I load something. And then again the next time I load ECL after that I get the error again. I am using Ubuntu 19.10. I have tried compiling the development branch from gitlab (wouldn't be the first time Ubuntu ships with a buggy package when upstream is fine) but I get the same behaviour. I did try using restart 1. to increase the stack size, but I just keep getting the error until I get an error about being unable to increase the stack size anymore. The error is the same that Zhou Qianliang reported in January, but I'm not doing anything odd, just trying to start ecl for a second time. https://mailman.common-lisp.net/pipermail/ecl-devel/2020-January/011473.html I have searched for the error message but not come up with anything much more than the above mailing list message. Error message: ;; Loading #P"/usr/local/lib/ecl-16.1.3/asdf.fas" An error occurred during initialization: The slot ASDF/PLAN::STAMP in the object #<action-status Condition of type: STACK-OVERFLOW BINDING-STACK overflow at size 10240. Stack can probably be resized. Proceed with caution. Available restarts: 1. (CONTINUE) Extend stack size 2. (RETRY) Retry ASDF operation. 3. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration. 4. (RETRY) Retry completing compilation for #<package-inferred-system "asdf">. 5. (ACCEPT) Continue, treating completing compilation for #<package-inferred-system "asdf"> as having been successful. 6. (RETRY) Retry ASDF operation. 7. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration. 8. (CONTINUE) Ignore initialization errors and continue. 9. (ABORT) Quit ECL unsafely, ignoring all existing threads. Top level in: #<process TOP-LEVEL 0x55b73cdd2f80>. > Thanks for any help you can give me. I'm looking forward to using ECL, seems like a nice platform! --querent.

3 3

AW: ASDF problem on second load of ECL
by marius.gerbershagen＠gmail.com 27 Feb '20

27 Feb '20

Hi, I have seen this problem occurring previously when asdf was trying to update itself. Unfortunately, the update process is so complicated that I wasn't able to determine whether the error is due to a bug in asdf or in ECL. Therefore, I can only offer you two possible workarounds: a) make sure that no copy of asdf is located somewhere where asdf is searching for its systems or b) create a monolithic asdf.lisp file from the asdf sources, drop it in place of contrib/asdf/asdf.lisp in the ECL sources and recompile ECL. Best, Marius Gerbershagen ----- Reply message ----- Von: "querent" <querent(a)yandex.com> An: <ecl-devel(a)common-lisp.net> Betreff: ASDF problem on second load of ECL Datum: Do., Feb. 27, 2020 10:57 Hi there, I am just trying to use ECL for a little project of mine, but I have a problem. Immediately after installation, things seem to work fine. I can run things, produce executables, etc. However, the second time I load ECL I get the error listed below. Deleting .cache/common-lisp/ecl-16.1.3 removes the error, but of course the world gets recompiled every time I load something. And then again the next time I load ECL after that I get the error again. I am using Ubuntu 19.10. I have tried compiling the development branch from gitlab (wouldn't be the first time Ubuntu ships with a buggy package when upstream is fine) but I get the same behaviour. I did try using restart 1. to increase the stack size, but I just keep getting the error until I get an error about being unable to increase the stack size anymore. The error is the same that Zhou Qianliang reported in January, but I'm not doing anything odd, just trying to start ecl for a second time. https://mailman.common-lisp.net/pipermail/ecl-devel/2020-January/011473.html I have searched for the error message but not come up with anything much more than the above mailing list message. Error message: ;; Loading #P"/usr/local/lib/ecl-16.1.3/asdf.fas" An error occurred during initialization: The slot ASDF/PLAN::STAMP in the object #<action-status Condition of type: STACK-OVERFLOW BINDING-STACK overflow at size 10240. Stack can probably be resized. Proceed with caution. Available restarts: 1. (CONTINUE) Extend stack size 2. (RETRY) Retry ASDF operation. 3. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration. 4. (RETRY) Retry completing compilation for #<package-inferred-system "asdf">. 5. (ACCEPT) Continue, treating completing compilation for #<package-inferred-system "asdf"> as having been successful. 6. (RETRY) Retry ASDF operation. 7. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration. 8. (CONTINUE) Ignore initialization errors and continue. 9. (ABORT) Quit ECL unsafely, ignoring all existing threads. Top level in: #<process TOP-LEVEL 0x55b73cdd2f80>. > Thanks for any help you can give me. I'm looking forward to using ECL, seems like a nice platform! --querent.

1 0

About the source of The ECL Manual
by NOEU 21 Feb '20

21 Feb '20

Hello. I want to translate "The ECL Manual(https://common-lisp.net/project/ecl/static/manual/)" into my native language (Japanese). Because I couldn't find the translated version. Is "The ECL Manual" generated by DocBook? Please let me know if I have a way to get the XML source for The ECL Manual. Thanks

2 2

Combining ~T and ~<~:;~>
by Eric Timmons 03 Feb '20

03 Feb '20

I've been using ECL to compile SBCL on aarch64, but I can't do it without patching the sources. There is a warning triggered during the build (only on aarch64) with a format string that contains: ~<~%~9T~:;~/sb-impl:print-type/:~> ECL chokes on this due to the ~T in the ~:; clause. Why is that not allowed? It seems like a reasonable thing to do at first glance. -Eric

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

ecl-devel February 2020