Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 22 Sep 2004 19:35:22 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: New packge: lighttpd-1.3.0
In-Reply-To: <618153225.20040923011821@familiehaase.de>
Message-ID: <Pine.GSO.4.61.0409221928410.27683@slinky.cs.nyu.edu>
References: <E1CA4ul-0006CO-00 AT mailhub-04 DOT inode DOT at> <41519C77 DOT 4080201 AT x-ray DOT at> <1656566026 DOT 20040922215552 AT familiehaase DOT de> <41520175 DOT AA068400 AT dessent DOT net> <618153225 DOT 20040923011821 AT familiehaase DOT de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Thu, 23 Sep 2004, Gerrit P. Haase wrote:

> Hello Brian,
>
> >> I hate this package since I tried to build it the first time.
>
> > Part of the problem here is that "We don't support building under
> > Cygwin" is the official line from php-dev.
>
> Sigh;)
>
> > I've got php-4.3.8 working fine as a DSO with Apache (a single 3.1M
> > chgphp4.dll.)  This works for whatever modules/extensions are statically
> > included, but obviously that's not quite acceptable.  If you
> > "--enable-foo=shared" you get a foo.a file in the modules dir, but this
> > is not a win32 executable and so it cannot be dlopen()'d.  I'm still
> > working on how to get these extension modules working, when I do I'll
> > ITP the whole batch.
>
> If it works on Linux to get .so shared modules, why should it not work
> on Cygwin to get the modules the same way?

It turns out that it does (I just got through the same pains with O'Caml,
which, BTW, will support dynamic loading as soon as I release the updated
package).  You can even name the libraries ".so" with no loss of function
(fewer changes to Makefiles), but I've only tested on WinXP.  The biggest
problem with Cygwin's shared modules is that any unresolved dependencies
have to be resolved at build time, so you end up with .so's depending on
other .so's, which have to be in the PATH.

> I have already half the way through, I'll hopefully get a shared
> library now and then I'll try to get the modules shared too.

I'd be glad to share my experiences of the O'Caml build (which also had an
added problem that it relied on .so's being able to load symbols from the
application that loaded them, a la Linux).  It turns out that, as long as
the dependencies can be found in the PATH and all the symbols are moved to
shared libraries, it wasn't that painful after all.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/