Hello everyone.
I have ECL (ver 1.4.1) which was compiled with
"./configure --enable-threads --enable-boehm --enable-unicode" on Mac
OS X 10.6.3.
I want to use multi-thread, so I tried to run threads examples
(source path is /examples/threads/import/import.c).
But freeze it with the following ou
On Thu, Jul 15, 2010 at 3:08 AM, Gabriel Dos Reis <
g...@integrable-solutions.net> wrote:
> Do you have a documentation for ECL's FASL format (and data structures)?
>
Not really: read.d and more precisely read_VV document the process of
initializing a FASL file, while load.d shows how it is load
On Fri, Jul 2, 2010 at 9:50 AM, Eric Marsden wrote:
> Compiling with --enable-unicode on Linux/AMD64 has become very
> RAM-consuming; I killed a recent compile with 3.5 GB resident during
> ecl_min compile. I'm building with only "--enable-unicode
> --enable-threads". Below is the stage reached i
The implications are simple: the developer / company / distributor must
provide a binary of their application which can be linked against a newer
version of ECL. No need for source distribution, no restriction w.r.t to
economics of the distribution.
Juanjo
On Sat, Jul 17, 2010 at 7:54 PM, Andy He
Note the implications of ECL's license (LGPL, unfortunately) when
considering statically linking with it.
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/fi
On Wed, Jul 7, 2010 at 1:16 AM, Pascal J. Bourguignon wrote:
> When loading :alexandria with asdf in ecl 10.7.1, there's a mix up
> with pathnames.
The example below shows clearly what is happening. ECL's TRUENAME,
PROBE-FILE and TRANSLATE-LOGICAL-PATHNAME seem to be working fine but ASDF
refus
On 17 jul 2010, at 16:28, Juan Jose Garcia-Ripoll > wrote:
On Sat, Jul 17, 2010 at 2:38 PM, Erik Winkels
wrote:
Is it possible to compile libecl.so as a static library as well?
Not "as well" but "solely". The configuration option --disable-
sahred does this.
Ah, thanks! I thought it just
On Sat, Jul 17, 2010 at 2:38 PM, Erik Winkels wrote:
> Is it possible to compile libecl.so as a static library as well?
Not "as well" but "solely". The configuration option --disable-sahred does
this.
> One of my goals for my ILGE 2010 entry was easy distribution of a binary
> executable and
Hello all,
Is it possible to compile libecl.so as a static library as well? I've
been looking through the docs and ./configure --help but didn't see it
and I'm wondering whether I missed something before I go dig deeper.
One of my goals for my ILGE 2010 entry was easy distribution of a binary
ex
