Re: status update

Oh my, I've been working on fixing something that's just not fixable
for the last day (reverse DNS lookup ... doesn't work on my test
windows machine, not even with nslookup.exe).

Source tarbal:
https://drive.google.com/file/d/0B303fG5hcio_bzR4SWszcnRoTWM/view?usp=sharing


> By that time I need to have an independent confirmation that you
> built clisp on windows with working rawsock module (that was the
> condition for the midterm "pass" from the get go).  Please make sure
> that I do get the confirmation by then.  Sorry if that sounds harsh,
> but rules are rules.

No problem. I'm a week behind schedule, and there's absolutely nothing
that you could've done / helped me with to prevent that.

CLISP with rawsock builds on windows, but it's not yet able to pass
all tests. The core tests hangs when trying to let another CLISP
instance send data via sockets to itself, but as far as I can see this
is an issue with the invocation of that second instance.

I removed the reverse DNS lookup from the rawsock tests, that way I
got the number of errors down to 13. These seem mostly to come from
the code that is sitting in syscalls module and core CLISP. On another
windows test machine rawsock tests give a stack overflow when testing
rawsock errors (the test that starts with "(block foo"), I don't know
why yet.

Regarding the independent confirmation: I'm a bit afraid that due to
the lack of remaining time this could be an issue (I don't know how
many are actively following this conversation). Is another GSoC
student independent enough? (I was thinking about asking for help on
the summer of code mailing list .. in order to have someone download
the source tarbal, build it and send the confirmation to clisp-list.)


> what are the changes you had to make to get it working?  it's
> important that the changes "scale", i.e., a gnulib update does not
> entail much work.

The changes to rawsock? Not that much, actually. I switched its build
system to one built with autotools, mostly in order to give it an
gnulib checkout of its own. I'm writing some gnulib modules to patch
functionality missing on windows (ifaddrs.h functions atm) so that the
code in rawsock can be completelty platform independent.

If by "scale" you mean that they can be built upon: Updating gnulib (when,
for example there's an update in a used module) means running

gnulib-tool --update

in modules/rawsock, followed by

autoreconf --force --install

This is the exact procedure I'm following whenever I've made a change
to one of the used modules.

Though, atm the code is messy: I copied some parts from core CLISP and
the syscalls module, although I don't use it. The reason is that both
core CLISP as well as syscalls are still using the old, not yet
updated gnulib code. Updating that failed due to the build system not
being able to "rebuild" itself (the configures target in
Makefile.devel fails).

Looking at how much time I wasted struggling with the build system I'd
like to replace it with an "standard" autotools one. I already started
work on that, it shouldn't be much of an issue.

I'd like to start a discussion about the modules and their
organization in general, but I'll write that in a separate message
soon.

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel