On 3/16/2015 2:28 PM, Blake McBride wrote:
> I noticed dynamic modules doesn't work on my 64 bit Linux either. I too
> am using the respository head. Any chances your patch will fix my
> problem too?
>
> If so, where do I get your patch?
The patches are pretty Cygwin-specific, but maybe there's an idea in
there that could help you. I'm attaching the current version. (It
could still change after further testing.)
Ken

I noticed dynamic modules doesn't work on my 64 bit Linux either. I too am
using the respository head. Any chances your patch will fix my problem too?
If so, where do I get your patch?
Thanks!
Blake McBride
On Fri, Mar 13, 2015 at 3:24 PM, Ken Brown <kbrown@...> wrote:
> On 3/6/2015 11:58 AM, Ken Brown wrote:
> > I used the configure option
> >
> > --without-dynamic-modules
> >
> > because dynamic modules currently do not work on Cygwin. My next goal
> > is to try to fix this. But I know that Reini worked on it without
> > success, so I'm not very optimistic.
>
> Just to follow up on this, it turned out that I was able to get it
> working after all. In case there are Cygwin users on this list who
> would like to try it, I've just updated Cygwin's clisp package:
>
> https://cygwin.com/ml/cygwin-announce/2015-03/msg00025.html
>
> I'll wait a couple weeks and then submit my patches if there are no
> problems reported.
>
> Ken
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> clisp-devel mailing list
> clisp-devel@...
> https://lists.sourceforge.net/lists/listinfo/clisp-devel
>

On 3/6/2015 11:58 AM, Ken Brown wrote:
> I used the configure option
>
> --without-dynamic-modules
>
> because dynamic modules currently do not work on Cygwin. My next goal
> is to try to fix this. But I know that Reini worked on it without
> success, so I'm not very optimistic.
Just to follow up on this, it turned out that I was able to get it
working after all. In case there are Cygwin users on this list who
would like to try it, I've just updated Cygwin's clisp package:
https://cygwin.com/ml/cygwin-announce/2015-03/msg00025.html
I'll wait a couple weeks and then submit my patches if there are no
problems reported.
Ken

On Fri, Mar 6, 2015 at 2:39 PM, Ken Brown <kbrown@...> wrote:
> On 3/6/2015 3:17 PM, Sam Steingold wrote:
>> Jerry, your patches have not been applied because, alas, CLISP has
>> fallen out of maintenance. We are sorry about that.
I understand. I'm an XEmacs developer. :-)
>> Ken, Jerry,
>> If you are interested, we can make either of you (or both) the new
>> maintainers.
>
>
> I'm not qualified. I'm not even a clisp user; I'm just working on build
> issues. But I'd be glad to help in any way I can if someone steps forward
> to be the new maintainer.
I regret that I don't really have sufficient free time to take on
another open source project. But I'm with Ken. If somebody does step
forward to take up maintenance, I will help with Fedora build and
integration issues, and supply the occasional patch as needed.
--
Jerry James
http://www.jamezone.org/

On 3/6/2015 3:17 PM, Sam Steingold wrote:
>> * Ken Brown <xoebja@...> [2015-02-24 17:06:49 -0500]:
>>
>> I have just taken over from Reini Urban as clisp maintainer for
>> Cygwin.
>
> Thank you!
>
>> I can build the tip of the Mercurial repository on both 32-bit and
>> 64-bit Cygwin [*], but several patches are required (not all of which
>> are Cygwin-specific). I would like to get these patches applied. How
>> should I proceed? Should I just send patches to this list? Or do you
>> prefer bug reports with patches attached?
>
> Sorry about nor replying right away.
> Please submit your patches to
> https://sourceforge.net/p/clisp/patches/
> (you will need an SF account).
OK.
> Jerry, your patches have not been applied because, alas, CLISP has
> fallen out of maintenance. We are sorry about that.
>
> Ken, Jerry,
> If you are interested, we can make either of you (or both) the new
> maintainers.
I'm not qualified. I'm not even a clisp user; I'm just working on build issues.
But I'd be glad to help in any way I can if someone steps forward to be the
new maintainer.
Ken

> * Ken Brown <xoebja@...> [2015-02-24 17:06:49 -0500]:
>
> I have just taken over from Reini Urban as clisp maintainer for
> Cygwin.
Thank you!
> I can build the tip of the Mercurial repository on both 32-bit and
> 64-bit Cygwin [*], but several patches are required (not all of which
> are Cygwin-specific). I would like to get these patches applied. How
> should I proceed? Should I just send patches to this list? Or do you
> prefer bug reports with patches attached?
Sorry about nor replying right away.
Please submit your patches to
https://sourceforge.net/p/clisp/patches/
(you will need an SF account).
Jerry, your patches have not been applied because, alas, CLISP has
fallen out of maintenance. We are sorry about that.
Ken, Jerry,
If you are interested, we can make either of you (or both) the new
maintainers.
(If either you or Ken is a student, you can apply to GSoC 2015 to do
that and get paid in the process. The success indicator will be
releasing CLISP 2.50 for Linux, Windows, Cygwin, MacOSX, and at least
one of FreeBSD, OpenBSD and NetBSD).
Thanks.
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1344
http://www.childpsy.net/http://iris.org.ilhttp://americancensorship.orghttp://think-israel.orghttp://ffii.orghttp://honestreporting.com
My inferiority complex is not as good as yours.

On 2/24/2015 5:06 PM, Ken Brown wrote:
> I have just taken over from Reini Urban as clisp maintainer for Cygwin.
> I can build the tip of the Mercurial repository on both 32-bit and
> 64-bit Cygwin [*], but several patches are required (not all of which
> are Cygwin-specific). I would like to get these patches applied. How
> should I proceed? Should I just send patches to this list? Or do you
> prefer bug reports with patches attached?
Since no one answered this, and it's easier to send patches than to make
bug reports, I'll send a sequence of patches in separate emails.
The are 12 patches. The first 9 are intended to be applied to the
Mercurial repository. Patches 10 and 11 just update two configure
scripts so that the tip still builds. Presumably the maintainers should
regenerate the configure scripts instead of applying the patches
directly, but maybe it's convenient for them to apply the patches as a
temporary measure.
Patch 12 is definitely *not* to be applied; it simply disables the
building of regexp on 64-bit Cygwin because of the gcc problem mentioned
below. I'm sending it so that anyone who wants to try to replicate the
build can apply it locally.
Here are some further remarks for people who want to replicate the build:
1. I used the configure option
--without-dynamic-modules
because dynamic modules currently do not work on Cygwin. My next goal
is to try to fix this. But I know that Reini worked on it without
success, so I'm not very optimistic.
2. In the 64-bit case, I also used the following configure options:
--ignore-absence-of-libsigsegv --without-ffcall
3. The build fails with mysterious error messages (on both 32-bit and
64-bit Cygwin) unless the executables are built with a big enough stack.
I built with
LDFLAGS="-Wl,--stack,0x800000"
4. In the 64-bit case, the only modules I could build were rawsock and
dirkey. All others that I tried failed to build either because they
required ffcall or because they led to the gcc problem below.
Feedback on my patches is welcome. If I need to sign a copyright
assignment in order to get them applied, I'll be glad to do so.
Ken
> I ran into a gcc problem when trying to build several of the modules
> (including regexp):
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64939

On 3/2/2015 9:37 AM, Ken Brown wrote:
>> generational GC requires libsigsegv.
>
> Thanks. The build on 32-bit Cygwin uses libsigsegv but not generational
> GC, so there's no difference here between the 32-bit and 64-bit
> situations. I should probably look into why generational GC isn't used
> in the 32-bit case.
The problem turns out to be that clisp's configure doesn't like Cygwin's
mmap. I tried to build with -DHAVE_MMAP_ANON to see if this was just a
problem with the configure test, but the build failed with a complaint
about EXTRA-FILE-TYPES not being defined. I didn't pursue it further.
Ken

On 2/25/2015 3:58 PM, Don Cohen wrote:
> Ken Brown writes:
> > I have just taken over from Reini Urban as clisp maintainer for Cygwin.
> > I can build the tip of the Mercurial repository on both 32-bit and
> > 64-bit Cygwin [*]
>
> Where can we get this to try out?
My build of clisp-2.49 is already in the Cygwin distribution. If you
want to try my build of the tip specifically, I can make it available.
> > 1. ffcall has not been ported to 64-bit Cygwin.
> > 2. libsigsegv has not been ported to 64-bit Cygwin.
> Doesn't this affect GC ?
I'm a clisp novice; I don't really know the connection between
libsigsegv and GC.
> Or are you using a "memory model" that doesn't require it?
I'm just using whatever memory model is built by default. It seems to
work, so I haven't had to look into it in detail.
Ken

Ken Brown writes:
> I have just taken over from Reini Urban as clisp maintainer for Cygwin.
> I can build the tip of the Mercurial repository on both 32-bit and
> 64-bit Cygwin [*]
Where can we get this to try out?
> 1. ffcall has not been ported to 64-bit Cygwin.
> 2. libsigsegv has not been ported to 64-bit Cygwin.
Doesn't this affect GC ?
Or are you using a "memory model" that doesn't require it?