Hello,<br><br>About my modifications for Cygwin support, I will prepare all modifications in patches format instead complete files. <br><br>I will send you the patch at the end of August (before it is impossible to me)<br>
<br><br>But I need some help in order to solve the problems:<br><u><b><br>Regression Tests: </b></u><br><br>I have problems with 8 of 183 tests there are two kind of problems:<br> - "bind(): Address already in use"
<br> - "Test timed out"<br>Do you know if some platform have similar problems or some common cause of this errors?<br><br>I have executed same regression tests in Solaris 10, and the results are worse than Cygwin, Solaris has "20 of 183 tests failed" so if Solaris is level "B - Platforms we try not to break" we can consider Cygwin at its same level? or errors must be zero in order to add my modifications to subversion??<br>
<br><br><u><b>Autoconf tools (aka autocrap): </b></u><br><br>I am a newbie in autoconf world. I was able to make almost all modifications in <a href="http://configure.ac">configure.ac</a> but I need some manual changes in Makefile.am:<br>
<ul><li>Only for libraries, we need to add "-no-undefined" parameter in LDFLAGS</li><li>Only for varnishd, we need to add "-Wl,-out-implib,libvarnishd.dll.a" in LDFLAGS this changes only apply to Cygwin.</li>
<li>In Cygwin, the libraries "libvcl" and "libvarnishapi" have a new compilation-time dependence with libvarnish, I have to add LIBS=-lvarnish and LDFLAGS='-L$(top_builddir)/lib/libvarnish only for libvcl and libvarnishapi.</li>
<li>If platform is not cygwin, we do not add anything.<br></li></ul><br>I have apply the modifications defining some variables that in Cygwin have some value and in other platforms are blank. This variables are used in the specific Makefile.am.<br>
<br>There is other way to apply modifications without changing the five Makefile.am and only changing <a href="http://configure.ac">configure.ac</a> ???<br><br><br><u><b>Other questions:</b></u><br><br>Do you want me to reopen ticket #736 with changes or I must create a new ticket?<br>
<br>About "supported platform" in varnish I think there is no page in wiki (<a href="http://varnish-cache.org/wiki">http://varnish-cache.org/wiki</a>) that speaks about diferences between Linux, FreeBSD, Solaris and MacOSX support. <br>
Maybe the only page about platforms is: <a href="http://varnish-cache.org/wiki/Installation">http://varnish-cache.org/wiki/Installation</a> but only speaks about installation issues. In the future it will be necessary to add Cygwin at this page and speak about some debugging tricks of this platform (strace command or CYGWIN enviroment variable)<br>
<br><br><br>Thank you,<br><br>Jorge<br><br><br><br><br><div class="gmail_quote">2010/8/4 Varnish <span dir="ltr"><<a href="mailto:varnish-bugs@varnish-cache.org">varnish-bugs@varnish-cache.org</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">#736: Migration to Cygwin plataform<br>
----------------------+-----------------------------------------------------<br>
Reporter: jdzst | Type: enhancement<br>
</div> Status: closed | Priority: normal<br>
<div class="im"> Milestone: | Component: build<br>
Version: | Severity: normal<br>
</div>Resolution: invalid | Keywords: cygwin, windows<br>
----------------------+-----------------------------------------------------<br>
<div class="im">Changes (by phk):<br>
<br>
* status: new => closed<br>
</div> * resolution: => invalid<br>
<br>
<br>
Comment:<br>
<br>
Your ticket and work with cygwin caused me to ponder what we mean by<br>
"supported platform" in Varnish, and I wrote up my thoughts yesterday:<br>
<br>
<a href="http://varnish-cache.org/browser/trunk/varnish-" target="_blank">http://varnish-cache.org/browser/trunk/varnish-</a><br>
cache/doc/sphinx/phk/platforms.rst<br>
<br>
CYGWIN is a Tier C platform, one we are willing to tolerate, if it does<br>
not cost us too much effort.<br>
<br>
These changes do not look terribly intrusive. (I don't understand why you<br>
have to modify all the Makefile.am to add cygwin specific LD-flags, I<br>
thought autocrap did that for you ?)<br>
<br>
On the other hand, you don't seem to have managed to get much<br>
functionality out of it yet, given that some of those failing tests are<br>
very basic functionality.<br>
<br>
But keep at it, send us patches instead of complete files, once you get<br>
the test-cases to work, and we will give you a fair reading.<br>
<br>
For now I will close this ticket.<br>
<font color="#888888"><br>
--<br>
Ticket URL: <<a href="http://www.varnish-cache.org/ticket/736#comment:7" target="_blank">http://www.varnish-cache.org/ticket/736#comment:7</a>><br>
</font><div><div></div><div class="h5">Varnish <<a href="http://varnish-cache.org/" target="_blank">http://varnish-cache.org/</a>><br>
The Varnish HTTP Accelerator<br>
</div></div></blockquote></div><br>