This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On 11/1/2012 5:08 PM, Ralph Castain wrote:
> I think we'd be interested in looking at possibly adding this to the
> code base. We still need to announce this (and will shortly), but our
> Windows maintainer has moved on to other pastures. So support for native
> Windows operations is ending with the 1.6 series, barring someone
> stepping up to fill the void.
> Having a cygwin alternative would let people at least continue to work
> on the Windows platform, albeit in a different mode. Is this something
> you are interested in pursuing?
there is no special code on my packages, so deploying a cygwin package
was already on my plan.
It will be just an addition to the other packages for which I am already
the cygwin package maintainer
I want just to be sure that it works as expect before deploying it,
and testing on a notebook is a bit limited.
The only peculiarity I noticed is that the stripped binaries do
not work, so the current package is based on unstripped installation.
Other step is to look if other options can be enabled:
LDFLAGS="-Wl,--export-all-symbols -no-undefined" \
at least "shmem-sysv" should be possible.