[Ecls-list] Help needed, really

Gabriel Dos Reis gdr at integrable-solutions.net
Tue Jan 4 11:10:55 UTC 2011


On Mon, Jan 3, 2011 at 10:13 AM, Samium Gromoff
<_deepfire at feelingofgreen.ru> wrote:
> I am replying to several mails, by different authors here, sorry for
> that.
>
> On Sat, 01 Jan 2011 13:13:36 -0600, Gabriel Dos Reis <gdr at cs.tamu.edu> wrote:
>> At the moment, since the discussion is stall and it does not appear that
>> ECL is willing to make itself more useful (at least as far as OpenAxiom
>> is concerned) on these multilib-platforms, and after reading indication
>> that ECL intentionally put misleading information regarding platforms on
>> *FEATURES*, I've disabled attempts to build OpenAxiom with ECL on know
>> problematic platforms.
>
> My impression was that ECL doesn't /add/ information anywhere -- it merely
> /forwards/ whatever is fed to it by autoconf.  It's not intent, merely a
> lack of sophistication.

Yeah, there was an earlier assertion by Juanjo:
# I already mentioned the problem with exporting Autoconf's detection
of processor,
# which on some platforms is flawed (intentionally, btw).


It has been a long day and a short night, and I'm a bit jet lagged.
I don't see this discussion getting anywhere, and I don't see any chances
of progress now when I'm jet lagged than when I was not.  I already
said I was dropping the issue.

My naivete has been to think from the outset, when I reported what was
causing the build failure and made suggestion (that was shut down based on
completely different interpretation of what I meant) that it was just a question
of explaining and if I tried hard enough it should be resolved.  However, what
ensued proved me wrong.  and the discussion over the week has significantly
cut into any appetite I had developed over the last couple of years
in contributing to make ECL a better alternative to other Lisp systems
out there.
I certainly was disposed to help implement missing features if the proposal was
deemed of interest (and of course subject to improvements.)  We never got to
that point, I doubt we ever will.
Reading past messages suggests that most ECL users who expressed themselves
are either against, or don't care, or seem to understand but believe
it is not an ECL
problem.  The choice I am left with to deal with it in a way that would not
unproductively consume more time, and that would not put me in this burlesque
situation.




More information about the ecl-devel mailing list