Hello,
I'm not aware of this bug. Please file it on the gitlab (with steps to
reproduce – may be some source files with instructions how to build).
Thanks,
Daniel
Fabrizio Fabbri writes:
> Hi all,
> I'm on my win64 build and I'm using asdf to define my system but with
> asdf:make-build or
> as
Hello,
what unit test you talk about?
Regarding the windows port, except msvc we have also mingw support (it
has some problems now though), and cygwin – both work fine with
autoconf.
Regards,
Daniel
Fabrizio Fabbri writes:
> Hi all,
> I make ECL compile with Win64 cl compiler, and so far it do
Hello,
to change the temporary dir you may set the logical-pathname-translation
of "TMP":
(setf (logical-pathname-translations "TMP")
`(("**;*.*.*" ,(merge-pathnames "/your/new/directory/" "**;*.*.*"
(or something like this). But I think that the problem is cache
directory, which
Hi all,
I make ECL compile with Win64 cl compiler, and so far it does not work
bad.
I want to run the unit test, and I was able to do it manually
with some failure but I'm not 100% sure that I run those in the right
way.
It there some instruction that I can follow or can you tell me wich is
the p
Hi all,
I'm on my win64 build and I'm using asdf to define my system but with
asdf:make-build or
asdf:load-bundle-op the ld-flags option to link some additional static
library to my fasl is not passed to the linker.
So far I workaround with (si:setenv "_CL_" "bla bla bla") but it's not
ideal.
A
Hi,
We have a few different c++ projects with ecl embedded, which when starting
up, have ecl compiling and loading quite a bit of lisp code.
If we start the various processes close enough in time, conflicts occur
while compiling the lisp code. All is good if I wait for the lisp
compilations betwe
