[Ecls-list] More precise scanning

[Gabriel Dos Reis]

On Tue, Feb 2, 2010 at 10:00 AM, Juan Jose Garcia-Ripoll
<juanjose.garciaripoll at googlemail.com> wrote:
> On Tue, Feb 2, 2010 at 9:42 AM, Gabriel Dos Reis
> <gdr at integrable-solutions.net> wrote:
>>
>> On Tue, Feb 2, 2010 at 2:01 AM, Juan Jose Garcia-Ripoll
>> <juanjose.garciaripoll at googlemail.com> wrote:
>> > On Tue, Feb 2, 2010 at 8:31 AM, Yue Li <xyly781 at gmail.com> wrote:
>> >>
>> >> On Mon, Feb 1, 2010 at 9:46 AM, Juan Jose Garcia-Ripoll
>> >> <juanjose.garciaripoll at googlemail.com> wrote:
>> >> > I have implemented a new option, --enable-precisegc, which is linked
>> >> > to
>> >> > new
>> >> > ways of using the garbage collector.
>> >>
>> >> I was trying to rebuild the ECL from cvs, but the building is broken.
>> >
>> > Are you using ECL's garbage collector or is there a pre-installed
>> > version in
>> > your system? To me it seems the last case. I should probably condition
>> > the
>> > new code on the use of ECL's own version.
>>
>> I can reproduce the build error on my machine (openSUSE-11.1/x86_64.)
>> I saw that the GC library (libgc.a and libcord.a) was built as part of
>> simple
>>
>>     ./configure --enable-threads --enable-precisegc
>>     make
>
> Argg, I had not tried with threads enabled. I received a few more pointers
> from the garbage collector mailing list about how to include the headers in
> order to minimize dependencies. This should solve the problem.

Indeed, I can report that I just finish a build for a freshly updated
ECL CVS tree.
Thanks.

> In addition
> to this, I have conditionalized the use of --enable-precisegc on the use of
> the included garbage collector. This is needed because we have to use the
> collector's internal structures.

I hope that does not create too much of dependency to a particular version
of the collector.

-- Gaby