Hello,
ECL project page says the last release is 10.7.1, but I can't find it at
sourceforge (the last tarball is 10.4.1).
Also I don't see tag 10.7.1 in CVS.
Is it a typo at the project page?
Best regards,
- Anton
--
Hello.
I just successfully cross-compiled ECL head (git revision
09ae1f43c0cf244cdba5c9690e301c8a1aab2458) for ARM (arm9tdmi, linux).
Minor fixes were required.
1. chmod + ecl_min and dpp in the installation of build ecl, in the directory
{prefix}/lib/ecl-10.7.1/
2. Fixes in the generated
And one more minor note.
When you start (cross compiling) configure first time, information message says:
..
### 1) Vital information cannot be determined at configuration time
### because we are not able to run test programs. A file called
###
### has been created, that you will
20.01.2011, 14:55, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com:
On Thu, Jan 20, 2011 at 12:31 PM, Anton Vodonosov avodono...@yandex.ru
wrote:
It's a good idea, thanks. I will only need to think about race conditions,
like if GC starts after the sigwait returns, but before
Actually, the error is reproduced simply by creating a file test.lisp:
(defpackage test)
Then start ECL and do
(compile-file test.lisp)
;;; Compiling test.lisp
Cannot print object #TEST package readably.
Available restarts:
1. (RESTART-TOPLEVEL) Go back to Top-Level REPL.
Broken at
Hello.
The current HEAD has broken cross compilation. The problem is that the check
for __builtin_return_address function is not handled via the build/cross_config
file.
I fixed it by specifying an environment variable in the build/cross_config
and checking for the variable in the configure.
Hello.
When I debug compiled functions, I can't inspect local variables. Is it
supposed to work so, or it's a bug or maybe I am doing something wrong?
For example this functions. After compilation, locals are not available in the
debugger:
(defun test(a b c)
(declare (optimize (debug 3)
I had this error too! (I thought it's the result of the small changes in ECL
I made. So it's a relief to hear it wasn't me).
I also don't know how to reproduce it reliably. I saw there is only two
places in the ECL sources where this error message is printed.
If I have more info, I'll post it
I think you are right.If fork() in cygwing produces non-working ECL - it's serious bug of cygwin.It makes sense to file a bug report to cygwin. And create an ECL issue tracker ticket "ext:run-program not working on cygwin because of broken form() system call" which explains the reason. The ticket
Juan Jose Garcia-Ripoll:I am considering including http.lisp in the contributed sources, packaging it differently, but adding the original license. This would allow the test suite to 1) download quicklisp, sandbox it and test a set of libraries, 2) download the ansi test suite and run it and 3)
So you want users to execute quicklisp library tests as you run on your test farm? I am working on something similar. I want to suggest CL users to run a simple command, like (test-grid:run-tests),it will execute tests and upload statistics to central server. The statistics include library test
I resubmitted it to the but tracker:
https://sourceforge.net/tracker/index.php?func=detailaid=3462618group_id=30035atid=398053
and also reported to quicklisp:
https://github.com/quicklisp/quicklisp-client/issues/46
--
Hello.
Juan Jose, do you have plans to make a new release?
There were significant changes since the last release. And some bugs fixed.
In particular, the old release doesn't work with the last quicklisp.
Giving a version number to the HEAD would be good IMHO.
Best regards,
- Anton
Hello.
I have code similar to this:
(handler-case (quicklisp:quickload :some-library)
(serious-condition (condition) (my-error-handler))
When I run it on ECL and C compiler returns error from compiling .c file,
I have the following (despite the handler-case):
Error code 2 when executing
compiler is in use)
31.05.2012, 02:16, Anton Vodonosov avodono...@yandex.ru:
Hello.
Juan Jose, could you explain or point to docs about right way to deal with
two compilers?
Supposing ECL is build with ECL_CMP = 1 both compilers are included, right?
Is it possible to enable lisp-to-c
31.05.2012, 13:04, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com:
In principle, (load sys:cmp) used to do the trick, but that seems like a
hack. Hence, I will add a new function, C:INSTALL-C-COMPILER, to do the job.
If I didn't (load sys:cmp) and do not call
31.05.2012, 01:22, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com:
With the latest fixes of today I think that ECL is ready for a new release.
The most recent commit iscommit d545918cddedab3a5f1d5604a792159f2769c607
I would appreciate if you could test it and give me the ok.
I
23.07.2012, 17:30, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
Is it possible to reproduce your tests with my own platforms?
Yes, it is one of the primary goals to make it easy to run tests for everyone
and to share the results.
If you are interested, I will provide you
24.07.2012, 01:48, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
Juan Jose, thanks for the valuable feedback, I have increased the
priority for the separate status value for build failure (even higher
priority than starting to improve reports). And also realized
that it makes sense to
To me ecl-quicklisp sounds like some kind of customized or branched quicklisp.
The package provides two function: automatic installation of quicklisp
and hooking quicklisp into REQUIRE. Juan Jose, other functions you mention
are outside of quicklisp this package - monolitic fasls for libraries
09.08.2012, 01:55, Anton Vodonosov avodono...@yandex.ru:
I wish the the standard declare some *REQUIRE-HOOKS*
...
BTW, Juan Jose what do you think of exposing such a functionality
from ECL
People on comp.lang.lisp pointed me to ext:*module-provider-functions*
already existing in ECL
Hi, probably you have reasons to keep your old clonned repository,
but I have just clonned fresh repo from new sourceforge location.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's
An ECL problem is discussed in this thread:
http://lists.common-lisp.net/pipermail/cl-plus-ssl-devel/2012-September/000266.html
(the list archive doesn't contain all the 4 messages, so I will duplicate here
a little:
here is a log of flexi-sterams test suite with ECL bytecode compiler:
17.09.2012, 00:35, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
The fix is uploaded. I still have to see its interaction with other code --
libraries, for instance. Hopefully there are no other parts of ECL that
relied on the hardcoded function names.Juanjo
Have you pushed it to
FWIW, I've run the cl-test-grid tests (testsuites of 56 libraries, and
compilation/loading of all
the ASDF systems found in Quicklisp). No regressions comparing to ECL 91356f2d.
21.09.2012, 01:12, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
This is was latest commitcommit
ECL is ANSI compatible.
ASDF not created? How's that? If you post the output
here, we will be able to understand what is the error.
28.09.2012, 04:13, z_axis z_a...@163.com:
The ECL created stumpwm executable is smallest compared with SBCL, CCL and
CLISP. However, only the ECL executable
Hello Juan Jose.
I have tested the last git version of ECL - e90b2f12, and compared it with
one of the recent versions tested not so far ago - ce653d88.
Please check this report:
http://common-lisp.net/project/cl-test-grid/ecl-lisp-to-c.html
It presents only results which are different on the
Hi,
I am glad to hear this. Does it help to find real regressions?
I see that according reports situation is not always improving with commits.
Best regards,
- Anton
26.11.2012, 02:54, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
Dear Anton,thanks once more for your wonderful work
I mean only the bugs the alreay fixed.
Suppose new user comes to the mailing list and asks:
- I want to use ECL, what version do you recomment?
Release 12.7.1 or some version from source control repository?
If the answer is a version from source control, than it makes sense to name
this
09.12.2012, 01:45, Anton Vodonosov avodono...@yandex.ru:
Try to update quicklisp to the recent version
I mean quicklisp client, (ql:update-client) executed in some other lisp.
--
LogMeIn Rescue: Anywhere, Anytime
29.11.2012, 01:21, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
On Mon, Nov 26, 2012 at 11:06 PM, Anton Vodonosov avodono...@yandex.ru
wrote:
I see that according reports situation is not always improving with commits.
It turns out that the code I used for sorting reports
Hi.
Fist about the things that look strange now.
21.12.2012, 01:30, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
Indeed. There are reappearances which are some mysterious and I believe there
is some non-reproducibility of some results.
Non-reproducibility is quite rare. If test
21.12.2012, 03:43, Anton Vodonosov avodono...@yandex.ru:
I will try perform this procedure running tests from my machine. Will first
compare 12.12.1 with the current head.
If you will like how it works, we could then setup it for you.
So, I've compared release 12.12.1 and the current HEAD
28.12.2012, 00:17, Peter Enerccio enerc...@gmail.com:
When I try to use ecl with emacs and slime, if I need to change the method to
a different one, with different lambda list, I get an error out of which I
can't recover in any sensible way, so I have to stop the ecl and start is
again and
07.01.2013, 02:23, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
Dear Anton, thanks again for your work on this and for the good news.. It
seems your manual comparison of versions works better than the automated
process I tried to construct. Would it be very difficult to set up
I hare retested the current HEAD - bc13fb41.
It has the same regressions as 89a8201b.
I published the diff for bc13fb41 as separate reports:
http://common-lisp.net/project/cl-test-grid/ecl/2/ecl-diff-lisp-to-c.html
http://common-lisp.net/project/cl-test-grid/ecl/2/ecl-diff-bytecode.html
Best
IMHO, even if this is a bug, it affects very little code, and there is a easy workaround for this code, to rewrite as explisit calls to LIST, etc
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
30.01.2013, 21:19, Peter Enerccio enerc...@gmail.com:
I was wondering if it is possible to compile asdf package into single fas
file for easy loading/packaging.
I know it is possible, although can't provide further instructions as I never
used this feature.
Maybe others on this list can help
detected:
LOAD: Could not load file
#P/media/home/home/enerccio/projects/gaia/gaia/plugins/crap.fas (Error:
/media/home/home/enerccio/projects/gaia/gaia/plugins/crap.fas: file too
short)
Backtrace:
NIL
2013/1/30 Anton Vodonosov avodono...@yandex.ru
In CL you usually can't get stack trace out
?
2013/1/31 Anton Vodonosov avodono...@yandex.ru
31.01.2013, 17:13, Peter Enerccio enerc...@gmail.com:
Hello
as part of my compilation of the c backend, I also compile few lisp files
into fasls with
ecl --compile. I wonder if it is possible to change/add more flags for the
compiler
03.02.2013, 05:34, Peter Enerccio enerc...@gmail.com:
I actually got it working, so it was most likely problem on my side. Thanks!
Could you share your findings? What is the right reciepe for printing backtrace?
--
The
13.03.2013, 22:01, Robert Dodier robert.dod...@gmail.com:
Hello,
I am working with Maxima and I'd like to get a backtrace of
function calls. :backtrace doesn't provide much info -- it prints
just one stack frame (namely RUN). Is there a way to enable
:backtrace to print a frame for every
05.03.2013, 01:25, "Juan Jose Garcia-Ripoll" juanjose.garciarip...@gmail.com:On Mon, Mar 4, 2013 at 5:30 PM, Christian Schafmeister chris.sc...@verizon.net wrote:I've created a new implementation of Common Lisp that has a core written in C++ completely from scratch but hosts the ECL Common Lisp
I have been investigating whether ECL works on OS X and according to the
project page,
the OS X is not in the list of supported OSes.
Good thing I remembered this announcement so I assume ECL works.
BTW, as I don't have OS X, but it would be interesting to see some screenshots.
Best regards,
-
07.04.2013, 00:22, Pascal J. Bourguignon p...@informatimago.com:
Anton Vodonosov avodono...@yandex.ru
writes:
I have been investigating whether ECL works on OS X and according to
the project page, the OS X is not in the list of supported OSes.
Good thing I remembered this announcement so
05.03.2013, 01:25, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
On Mon, Mar 4, 2013 at 5:30 PM, Christian Schafmeister
chris.sc...@verizon.net wrote:
I've created a new implementation of Common Lisp that has a core written in
C++ completely from scratch but hosts the ECL Common
06.07.2013, 03:16, Yuri Albuquerque yuridenom...@gmail.com:
I'm scratching my head with some issues I'm having regarding ECL on android
(I'm using these patches: https://github.com/ageneau/ecl-android).
But the documentation only talks about how to build ECL. It does not talk
about what I'm
06.07.2013, 10:00, Matthew Mondor mm_li...@pulsar-zone.net:
On Sat, 06 Jul 2013 09:38:20 +0400
Anton Vodonosov avodono...@yandex.ru wrote:
1 - Licensing/the ecl-android build process. ECL is LGPL, which means I
can't statically link against it without open sourcing my project (which I
(and shipped with ECL).
On Sat, Jul 6, 2013 at 9:18 PM, Anton Vodonosov avodono...@yandex.ru wrote:
Hello.
New quicklisp 2013-06-15 has some regressions - some libraries that loaded
OK previously now fail to load.
Here is the diff of test results between quicklisp 2013-06-15
and the previous
07.07.2013, 00:17, Yuri Albuquerque yuridenom...@gmail.com:
But what about the build process? Should I simply load my code using ASDF?
I do not understand this. There are about 30 threads discussing how to build
shared libraries or statically linked libraries from user code using ASDF's
11.07.2013, 16:40, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
On Thu, Jul 11, 2013 at 2:04 PM, Anton Vodonosov avodono...@yandex.ru wrote:
I think (hope) there are not so many places in CL which allow to couple the
code with the host compiler.
Maybe this example with most
Hello.
I have just noticed :relative-package-names in features, in ECL.
Does ECL support relative package names? I somehow missed this information.
Is it the same API as SBCL and ABCL implement?
Best regards,
- Anton
Juan Jose, how about publishing the changes already in git as the last release?So that future users use and discuss a version as close to git repository as possible. 07.10.2013, 12:55, "Juan Jose Garcia-Ripoll" juanjose.garciarip...@gmail.com:Hi everybody, as you may have noticed, my level of
When I do 'make clean configure make'
the build fails with message:
make[4]: *** No rule to make target `mpn/add_n.lo', needed by `libgmp.la'.
Stop.
make[4]: Leaving directory `/home/testgrid/lisps/ecl-git/build/gmp'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
Oct 15 10:15:20 2013 +0200
Fixed Automake'd files that were broken by Cygwin's copy.
Best regards,
- Anton
15.10.2013, 12:16, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
On Sat, Oct 12, 2013 at 10:30 PM, Anton Vodonosov avodono...@yandex.ru
wrote:
When I do 'make clean
15.10.2013, 11:54, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
On Sat, Oct 12, 2013 at 12:56 AM, Anton Vodonosov avodono...@yandex.ru
wrote:
Juan Jose, how about publishing the changes already in git as the last
release?
So that future users use and discuss a version as close
07.10.2013, 12:55, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
* On a similar line, if integrating third-party libraries becomes an issue,
they will be completely dropped or frozen. For instance, ECL may end up
demanding
that you install libffi or libgc, leaving an old but
Jon, I have build 44c86e08.
It is some version after 13.5.1 release
19.10.2013, 18:46, Jon Boone ipmon...@gmail.com:
Anton,
What was the last commit that you tried that worked successfully?
--jon
On 2013-10-17, at 20:08, Anton Vodonosov avodono...@yandex.ru wrote:
Unfortunately I
21.10.2013, 16:53, Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com:
I am sorry for the prolonged silence. I wanted to give some time for my
message to settle in the community, but since I have seen a lot of
interesting discussion we should make use of this momentum to get something
22.10.2013, 17:11, Dietrich Bollmann dietr...@formgames.org:
Wouldn't it be possible to integrate the testing and benchmarking in the
build process? something like 'make test' and 'make benchmark' generating
reports which then could be send to some email address?
People downloading and
With the latest commits, the HEAD builds now.
Best regards,
- Anton
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for
Hello.
Below is the diff between cl-test-grid results
for ECL release 13.5.1 and the curren HEAD - commit c8a4d98d.
The bytecode compiler:
http://common-lisp.net/project/cl-test-grid/ecl/ecl-diff-2-bytecode.html
The lisp to C compiler:
Hello.
Does ECL ever fork itself?
I am asking because when running cl-test-grid tests
we are observing ECL hanging during cl-6502 testsuite.
According to the logs, test-grid-agent kills the ECL process,
but nevertheless we sometimes find an ECL process remaining in the system.
I have tested
When we observed the child process, it was /usr/local/bin/ecl,
so if we assume it was forked to invoke C compiler, then it hung
before 'exec'.
I saw in src/sys/unixsys.d that ECL when forks itself
first coordinates the parent and child processes by
reading writing a byte to a pipe in the parent,
Hi.
There was a discussion in cl-test-grid google group
(https://groups.google.com/forum/#!topic/cl-test-grid/6uqyuj6Jy-0)
about timeouts when running ECL tests on MacOSX Maverick,
which uses clang as the C compiler.
What might be interesting to ECL users is that
clang takes much longer to
Hi,
I have tested the release with cl-test-grid.
The release has some differences comparing to the latest release candidate:
https://common-lisp.net/project/cl-test-grid/ecl/ecl-diff-9-lisp-to-c.html
https://common-lisp.net/project/cl-test-grid/ecl/ecl-diff-9-bytecode.html
Regressions:
27.02.2015, 15:38, Daniel Kochmański jackdan...@hellsgate.pl:
Hey,
thanks. It shouldn't. Fixed on rc branch.
You probably forgot to push.
Best regards,
- Anton
--
Dive into the World of Parallel Programming The Go
Hi Daniel,
I've run tests for the new release:
lisp to C compiler:
https://common-lisp.net/project/cl-test-grid/ecl/ecl-diff-3-lisp-to-c.html
bytecode compiler:
https://common-lisp.net/project/cl-test-grid/ecl/ecl-diff-3-bytecode.html
New release brings many improvements, but also some
Hello Daniel,
My main wish to you: the most important criterion - don't break ECL,
don't make it worse than it is today.
And thanks for your initiative to take care about the project.
From your list of goals, I think new release is the most important,
because HEAD is quite different from the
69 matches
Mail list logo
