ecl-devel November 2020

ecl-devel@common-lisp.net

10 participants
8 discussions

Monolithic build of static library
by Иван Трусков 01 Dec '20

01 Dec '20

Hello. I am trying to make a library that makes use of 'STR' package and link it into my C program. I presumed that using :monolithic t flag would result in the static library that contained all systems my library depends on. However it seems that is not the case. Here is my .asd file: (defsystem "embedded-console" :description "embedded console - ECL functions for smart snake game" :author "Ivan Truskov <trus19(a)gmail.com>" :components ((:file "embedded-console")) :depends-on ("str")) I am compiling the library with command: ecl -norc -eval '(require :ecl-quicklisp)' -eval '(push \"/my/src/dir/\" asdf:*central-registry*)' -eval '(asdf:make-build :embedded-console :type :static-library :move-here \#P\"/my/output/dir}\" :monolithic t )' -eval '(quit)' However, when i try to link with resulting library, this is what i get: ... undefined reference to `init_lib_CL_PPCRE' ... undefined reference to `init_lib_BASE' ... undefined reference to `init_lib_CL_UNICODE' ... undefined reference to `init_lib_CL_PPCRE_UNICODE' ... undefined reference to `init_lib_CL_CHANGE_CASE' ... undefined reference to `init_lib_STR' ... undefined reference to `init_lib_EMBEDDED_CONSOLE' And indeed, when i run nm over the built file embedded-console--all-systems.a, this is output: eclinitVtJU9J.o: 0000000000000000 b Cblock.10857 U cl_boot U cl_symbols U _ecl_frs_push U ecl_init_module U ecl_make_codeblock U ecl_process_env U _GLOBAL_OFFSET_TABLE_ U init_lib_BASE U init_lib_CL_CHANGE_CASE U init_lib_CL_PPCRE U init_lib_CL_PPCRE_UNICODE U init_lib_CL_UNICODE U init_lib_EMBEDDED_CONSOLE 0000000000000000 T init_lib_EMBEDDED_CONSOLE__ALL_SYSTEMS U init_lib_STR 0000000000000110 T main_lib_EMBEDDED_CONSOLE__ALL_SYSTEMS U _setjmp nm: cl-ppcre.a: File format not recognized nm: base.a: File format not recognized nm: cl-unicode.a: File format not recognized nm: cl-ppcre-unicode.a: File format not recognized nm: cl-change-case.a: File format not recognized nm: str.a: File format not recognized nm: embedded-console.a: File format not recognized What am i doing wrong? What should i change to get static library containing all systems i am intending to use (and maybe only them, if possible)?

3 3

Windows 10
by Garrett Dangerfield 29 Nov '20

29 Nov '20

I got the 20.4.24 tarball and actually managed to compile it on Windows 10 using cygwin gcc. Got it to run and it seems to work pretty well from what I've seen so far. However, the goal of my doing all this was to be able to link Lisp code to C/C++ code and compile-file doesn't want to work. With this simple lisp file named t2.lsp: (defun gpdtest () (print "we did it")) When I do this (when in the same directory): (compile-file "t2.lsp" :system-p t) I get this back: Condition of type: FILE-ERROR Filesystem error with pathname #P"SYS:CMP.NEWEST". Which makes no sense to me. If I do this: (probe-file "t2.lsp") I get back: #P"/cygdrive/c/Users/danger/gcl/t2.lsp" Thoughts? Apologies in advance if this is a stupid question. :-) Thanks, Garrett Dangerfield.

4 3

Fw: Windows 10
by Daniel Kochmański 28 Nov '20

28 Nov '20

Garrett: please put ecl-devel as the address (that may be my fault that I've hit reply earlier). Re your problem, please ensure, that c compiler is in the path. -------- Oryginalna wiadomość -------- ‎ 26 lis 2020, 20:45, Garrett Dangerfield napisał(a): I got a compile to work with Visual Studio. I set: ECL_CMP = 1 and it's at least trying to generate a .o file instead of an .fasc file. I'm running this: > (ext:install-c-compiler) ;;; Loading #P"C:/Users/danger/Downloads/ecl-20.4.24/msvc/cmp.fas" NIL > (compile-file "t2.lsp" :system-p t) ;;; ;;; Compiling t2.lsp. ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0 ;;; ;;; End of Pass 1.The system cannot find the file specified. ;;; Internal error: ;;; ** Could not spawn subprocess to run "cl". NIL T T > And its' creating these files: -rwxr-xr-x+ 1 danger None 1930 Nov 26 11:40 t2.c -rwxr-xr-x+ 1 danger None 395 Nov 26 11:40 t2.data -rwxr-xr-x+ 1 danger None 599 Nov 26 11:40 t2.eclh Thoughts? Were there other settings I needed to tweak during the ECL compile? Thanks, Garrett. On Thu, Nov 26, 2020 at 9:54 AM Garrett Dangerfield <garrett(a)dangerimp.com> wrote: Thanks, I found the section of the manual right after I clicked send, of course. Thanks. On Thu, Nov 26, 2020 at 9:50 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: You don't call configure on msvc build, check out install file and the manual Wysłano z aplikacji ProtonMail -------- Oryginalna wiadomość -------- ‎ 26 lis 2020, 17:58, Garrett Dangerfield napisał(a): So if I use Visual Studio, will I still use cygwin to do the ./configure? On Thu, Nov 26, 2020 at 8:55 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, 26 November 2020 17:51, Garrett Dangerfield <garrett(a)dangerimp.com> wrote: I tried your suggestions and I tried the cygwin patch as well, no luck, that's why I tried to pull cygwin out of the equation. Neither seem to be producing an EXE that could understand an external compiler. With the non-cygwin configuration, I'm baffled on why configure says things are kosher but the compile fails for missing file, though. Thoughts? No, sorry. All I can think of is using msvc. Generally ECL expects that he C compiler used will be the same compiler ECL was built with itself. Thanks, Garrett. On Thu, Nov 26, 2020 at 3:05 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: ECL may be build with cygwin/mingw, then it works with cygwin/mingw runtime. You may also use MSVC, then you need to enter the msvc directory and issue nmake (see documentation for more precise instructions). That said, did you try my previous suggestion with passing appropriate flags to cygwin? Regards, Daniel -- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu "Be the change that you wish to see in the world." - Mahatma Gandhi ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, 25 November 2020 23:11, Garrett Dangerfield <garrett(a)dangerimp.com> wrote: So I zapped the gcc/g++, etc. from cygwin and did an install of mingw 64 bit outside of cygwin. I added the big directory from that to my path. I did the "./configure --with-cmp=yes" and it finished: config.status: creating ecl/config.h config.status: creating ecl/config-internal.h Configuration complete. To build ECL, issue make in this directory. But make is failing: $ make cd build; make make[1]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' c doc gc atomic make[2]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' Making all in src make[3]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' make all-am make[4]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c -o atomic_ops.lo /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c libtool: compile: gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c -o atomic_ops.o gcc.exe: error: /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c: No such file or directory gcc.exe: fatal error: no input files compilation terminated. make[4]: *** [Makefile:610: atomic_ops.lo] Error 1 make[4]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' make[3]: *** [Makefile:473: all] Error 2 make[3]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' make[2]: *** [Makefile:475: all-recursive] Error 1 make[2]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' make[1]: *** [Makefile:129: libeclatomic.a] Error 2 make[1]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' make: *** [Makefile:65: all] Error 2 Obviously, on windows I still have to use cygwin as my shell because that's what configure expects. Thoughts? Thanks, Garrett. On Wed, Nov 25, 2020 at 10:03 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: So the problem seems to be quite clear: your ecl build doesn't have the C compiler enabled. When you configure the build, include --with-cmp=yes (or builtin). ./configure --prefix=/my/cygwin/prefix --with-cmp=yes make && make install Then C compiler should be available (you may still need to call (ext:install-c-compiler), you need to check it yourself because I don't remember whether bytecodes compiler is installed by default on cygwin, it is for msvc). If it still doesn't work, please include a result of calling this code snippet: (format t "~&~@{~12@A ~S~%~}" :version (lisp-implementation-version) :vcs-id (ext:lisp-implementation-vcs-id) :os (software-type) :os-version (software-version) :machine-type (machine-type) :features *features*)

2 2

Static Compilation Issues
by Ava Fox 28 Nov '20

28 Nov '20

I've been learning how to create static executables with ECL and was looking at the provided example that uses an ASDF system that has defined dependencies (https://gitlab.com/embeddable-common-lisp/ecl/-/tree/develop/examples/asdf_…). When following the readme, and building it as-is with Quicklisp fetching alexandria (the only dependency specified) it works fine. However, when I change that dependency to include a project such as drakma it compiles fine but then throws SIMPLE-ERROR when I run the resulting static executable, saying that various uiop/asdf packages and sb-bsd-sockets cannot be found. Exact error: Condition of type: SIMPLE-ERROR Package ((SB-BSD-SOCKETS . #<SB-BSD-SOCKETS package>)) referenced in compiled file NIL but has not been created Exact packages being listed as not being found: :sb-bsd-sockets, :uiop/filesystem, :uiop/os, :uiop/pathname, :asdf/operate, :asdf/lisp-action Any help or ideas would be appreciated, I am just unsure of where to go from here. ECL version: 20.4.24 Operating System: Linux Kernel 5.8.18

4 6

Re: Windows 10
by Daniel Kochmański 26 Nov '20

26 Nov '20

You don't call configure on msvc build, check out install file and the manual Wysłano z aplikacji ProtonMail -------- Oryginalna wiadomość -------- ‎ 26 lis 2020, 17:58, Garrett Dangerfield napisał(a): > So if I use Visual Studio, will I still use cygwin to do the ./configure? > > On Thu, Nov 26, 2020 at 8:55 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: > >> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >> On Thursday, 26 November 2020 17:51, Garrett Dangerfield <garrett(a)dangerimp.com> wrote: >> >>> I tried your suggestions and I tried the cygwin patch as well, no luck, that's why I tried to pull cygwin out of the equation. Neither seem to be producing an EXE that could understand an external compiler. >>> >>> With the non-cygwin configuration, I'm baffled on why configure says things are kosher but the compile fails for missing file, though. >>> >>> Thoughts? >> >> No, sorry. All I can think of is using msvc. Generally ECL expects that he C compiler used will be the same compiler >> ECL was built with itself. >> >>> Thanks, >>> Garrett. >>> >>> On Thu, Nov 26, 2020 at 3:05 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: >>> >>>> ECL may be build with cygwin/mingw, then it works with cygwin/mingw runtime. You may also use >>>> MSVC, then you need to enter the msvc directory and issue nmake (see documentation for more >>>> precise instructions). >>>> >>>> That said, did you try my previous suggestion with passing appropriate flags to cygwin? >>>> >>>> Regards, >>>> Daniel >>>> >>>> -- >>>> Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland >>>> TurtleWare - Daniel Kochmański | www.turtleware.eu >>>> >>>> "Be the change that you wish to see in the world." - Mahatma Gandhi >>>> >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>> On Wednesday, 25 November 2020 23:11, Garrett Dangerfield <garrett(a)dangerimp.com> wrote: >>>> >>>>> So I zapped the gcc/g++, etc. from cygwin and did an install of mingw 64 bit outside of cygwin. I added the big directory from that to my path. >>>>> >>>>> I did the "./configure --with-cmp=yes" and it finished: >>>>> config.status: creating ecl/config.h >>>>> config.status: creating ecl/config-internal.h >>>>> Configuration complete. To build ECL, issue make in this directory. >>>>> >>>>> But make is failing: >>>>> $ make >>>>> cd build; make >>>>> make[1]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' >>>>> c doc gc atomic >>>>> make[2]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' >>>>> Making all in src >>>>> make[3]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>>>> make all-am >>>>> make[4]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>>>> /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c -o atomic_ops.lo /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c >>>>> libtool: compile: gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c -o atomic_ops.o >>>>> gcc.exe: error: /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c: No such file or directory >>>>> gcc.exe: fatal error: no input files >>>>> compilation terminated. >>>>> make[4]: *** [Makefile:610: atomic_ops.lo] Error 1 >>>>> make[4]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>>>> make[3]: *** [Makefile:473: all] Error 2 >>>>> make[3]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>>>> make[2]: *** [Makefile:475: all-recursive] Error 1 >>>>> make[2]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' >>>>> make[1]: *** [Makefile:129: libeclatomic.a] Error 2 >>>>> make[1]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' >>>>> make: *** [Makefile:65: all] Error 2 >>>>> >>>>> Obviously, on windows I still have to use cygwin as my shell because that's what configure expects. >>>>> >>>>> Thoughts? >>>>> >>>>> Thanks, >>>>> Garrett. >>>>> >>>>> On Wed, Nov 25, 2020 at 10:03 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: >>>>> >>>>>> So the problem seems to be quite clear: your ecl build doesn't have the C compiler enabled. >>>>>> When you configure the build, include --with-cmp=yes (or builtin). >>>>>> >>>>>> ./configure --prefix=/my/cygwin/prefix --with-cmp=yes >>>>>> make && make install >>>>>> >>>>>> Then C compiler should be available (you may still need to call (ext:install-c-compiler), you need >>>>>> to check it yourself because I don't remember whether bytecodes compiler is installed by default >>>>>> on cygwin, it is for msvc). >>>>>> >>>>>> If it still doesn't work, please include a result of calling this code snippet: >>>>>> >>>>>> (format t "~&~@{~12@A ~S~%~}" >>>>>> :version (lisp-implementation-version) >>>>>> :vcs-id (ext:lisp-implementation-vcs-id) >>>>>> :os (software-type) >>>>>> :os-version (software-version) >>>>>> :machine-type (machine-type) >>>>>> :features *features*)

1 0

Re: Windows 10
by Daniel Kochmański 26 Nov '20

26 Nov '20

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, 26 November 2020 17:51, Garrett Dangerfield <garrett(a)dangerimp.com> wrote: > I tried your suggestions and I tried the cygwin patch as well, no luck, that's why I tried to pull cygwin out of the equation. Neither seem to be producing an EXE that could understand an external compiler. > > With the non-cygwin configuration, I'm baffled on why configure says things are kosher but the compile fails for missing file, though. > > Thoughts? No, sorry. All I can think of is using msvc. Generally ECL expects that he C compiler used will be the same compiler ECL was built with itself. > Thanks, > Garrett. > > On Thu, Nov 26, 2020 at 3:05 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: > >> ECL may be build with cygwin/mingw, then it works with cygwin/mingw runtime. You may also use >> MSVC, then you need to enter the msvc directory and issue nmake (see documentation for more >> precise instructions). >> >> That said, did you try my previous suggestion with passing appropriate flags to cygwin? >> >> Regards, >> Daniel >> >> -- >> Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland >> TurtleWare - Daniel Kochmański | www.turtleware.eu >> >> "Be the change that you wish to see in the world." - Mahatma Gandhi >> >> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >> On Wednesday, 25 November 2020 23:11, Garrett Dangerfield <garrett(a)dangerimp.com> wrote: >> >>> So I zapped the gcc/g++, etc. from cygwin and did an install of mingw 64 bit outside of cygwin. I added the big directory from that to my path. >>> >>> I did the "./configure --with-cmp=yes" and it finished: >>> config.status: creating ecl/config.h >>> config.status: creating ecl/config-internal.h >>> Configuration complete. To build ECL, issue make in this directory. >>> >>> But make is failing: >>> $ make >>> cd build; make >>> make[1]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' >>> c doc gc atomic >>> make[2]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' >>> Making all in src >>> make[3]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>> make all-am >>> make[4]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>> /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c -o atomic_ops.lo /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c >>> libtool: compile: gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c -o atomic_ops.o >>> gcc.exe: error: /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c: No such file or directory >>> gcc.exe: fatal error: no input files >>> compilation terminated. >>> make[4]: *** [Makefile:610: atomic_ops.lo] Error 1 >>> make[4]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>> make[3]: *** [Makefile:473: all] Error 2 >>> make[3]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' >>> make[2]: *** [Makefile:475: all-recursive] Error 1 >>> make[2]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' >>> make[1]: *** [Makefile:129: libeclatomic.a] Error 2 >>> make[1]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' >>> make: *** [Makefile:65: all] Error 2 >>> >>> Obviously, on windows I still have to use cygwin as my shell because that's what configure expects. >>> >>> Thoughts? >>> >>> Thanks, >>> Garrett. >>> >>> On Wed, Nov 25, 2020 at 10:03 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: >>> >>>> So the problem seems to be quite clear: your ecl build doesn't have the C compiler enabled. >>>> When you configure the build, include --with-cmp=yes (or builtin). >>>> >>>> ./configure --prefix=/my/cygwin/prefix --with-cmp=yes >>>> make && make install >>>> >>>> Then C compiler should be available (you may still need to call (ext:install-c-compiler), you need >>>> to check it yourself because I don't remember whether bytecodes compiler is installed by default >>>> on cygwin, it is for msvc). >>>> >>>> If it still doesn't work, please include a result of calling this code snippet: >>>> >>>> (format t "~&~@{~12@A ~S~%~}" >>>> :version (lisp-implementation-version) >>>> :vcs-id (ext:lisp-implementation-vcs-id) >>>> :os (software-type) >>>> :os-version (software-version) >>>> :machine-type (machine-type) >>>> :features *features*)

1 0

Re: Windows 10
by Daniel Kochmański 26 Nov '20

26 Nov '20

ECL may be build with cygwin/mingw, then it works with cygwin/mingw runtime. You may also use MSVC, then you need to enter the msvc directory and issue nmake (see documentation for more precise instructions). That said, did you try my previous suggestion with passing appropriate flags to cygwin? Regards, Daniel -- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu "Be the change that you wish to see in the world." - Mahatma Gandhi ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, 25 November 2020 23:11, Garrett Dangerfield <garrett(a)dangerimp.com> wrote: > So I zapped the gcc/g++, etc. from cygwin and did an install of mingw 64 bit outside of cygwin. I added the big directory from that to my path. > > I did the "./configure --with-cmp=yes" and it finished: > config.status: creating ecl/config.h > config.status: creating ecl/config-internal.h > Configuration complete. To build ECL, issue make in this directory. > > But make is failing: > $ make > cd build; make > make[1]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' > c doc gc atomic > make[2]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' > Making all in src > make[3]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' > make all-am > make[4]: Entering directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' > /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c -o atomic_ops.lo /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c > libtool: compile: gcc -DHAVE_CONFIG_H -I../src -I/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src -Wall -Wextra -Wpedantic -Wno-long-long -g -O2 -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c -o atomic_ops.o > gcc.exe: error: /cygdrive/c/Users/danger/Downloads/ecl-20.4.24/src/bdwgc/libatomic_ops/src/atomic_ops.c: No such file or directory > gcc.exe: fatal error: no input files > compilation terminated. > make[4]: *** [Makefile:610: atomic_ops.lo] Error 1 > make[4]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' > make[3]: *** [Makefile:473: all] Error 2 > make[3]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic/src' > make[2]: *** [Makefile:475: all-recursive] Error 1 > make[2]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build/atomic' > make[1]: *** [Makefile:129: libeclatomic.a] Error 2 > make[1]: Leaving directory '/cygdrive/c/Users/danger/Downloads/ecl-20.4.24/build' > make: *** [Makefile:65: all] Error 2 > > Obviously, on windows I still have to use cygwin as my shell because that's what configure expects. > > Thoughts? > > Thanks, > Garrett. > > On Wed, Nov 25, 2020 at 10:03 AM Daniel Kochmański <daniel(a)turtleware.eu> wrote: > >> So the problem seems to be quite clear: your ecl build doesn't have the C compiler enabled. >> When you configure the build, include --with-cmp=yes (or builtin). >> >> ./configure --prefix=/my/cygwin/prefix --with-cmp=yes >> make && make install >> >> Then C compiler should be available (you may still need to call (ext:install-c-compiler), you need >> to check it yourself because I don't remember whether bytecodes compiler is installed by default >> on cygwin, it is for msvc). >> >> If it still doesn't work, please include a result of calling this code snippet: >> >> (format t "~&~@{~12@A ~S~%~}" >> :version (lisp-implementation-version) >> :vcs-id (ext:lisp-implementation-vcs-id) >> :os (software-type) >> :os-version (software-version) >> :machine-type (machine-type) >> :features *features*)

1 0

Question on multiple contributions to common-lisp.net...
by Lauren Blane 04 Nov '20

04 Nov '20

Hi, Hope you're having a great week! I'm Lauren from Business Collective. Your site, common-lisp.net, has sparked my interest to contribute articles and resources in the various topics that you cover. I especially enjoyed one of your latest posts, and therefore decided to reach out to you. I write on a broad range of topics and depending on what works best for you, I am definitely open to proposing and discussing ideal content titles that will benefit your site. If this sounds appealing to you, I’d love to have a conversation about how we could make it work. On that note, a long term partnership is the ideal goal in mind and would love to hear back from you ! Thanks gratefully, LaurenDon't want emails from us anymore? Reply to this email with the word "UNSUBSCRIBE" in the subject line.

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

ecl-devel November 2020