Hello,
With today's ECL (pulled from git), there are problems when building
swank with undefined 'c' errors. It turns out that some C generated
files have the following:
value0 = c;
An example:
{
cl_object V3; /* CONDITION */
V3 = ECL_CONS_CAR(CLV0);
cl_env_copy->nvalues = 2;
cl_env_copy->values[1] = V3;
cl_env_copy->values[0] = Cnil;
value0 = c;
ecl_frs_pop(cl_env_copy);
V2 = value0;
goto L1;
}
I however could compile some custom projects with it; although for
final executables I also now had to my build scripts for the link stage
to work (this was not necessary previously):
(setf C::*COMPILE-IN-CONSTANTS* t)
I did not check yet why my software builds yet swank doesn't and could
not take the time to look at the compiler source changes yet.
Thanks,
--
Matt
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Ecls-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecls-list
