Re: New Cygwin maintainer

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


------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel