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
Message-ID: <072801c5c46c$5a2dcbf0$5304a8c0@chimaera>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Tod" <tod AT madtoon DOT net>, "Cygwin" <cygwin AT cygwin DOT com>
References: <433AA6CD DOT 8010505 AT madtoon DOT net> <05f501c5c451$ae5eca50$5304a8c0 AT chimaera> <433AD19A DOT 4000208 AT madtoon DOT net>
Subject: Re: Compiling Apache2 under Cygwin with .so support
Date: Wed, 28 Sep 2005 21:36:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=response
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Please keep replies on the mailing list.
I'm taking this conversation back on-list.

Tod wrote:
> Max Bowsher wrote:
>> Tod wrote:
>>
>>> I'm trying to compile Apache 2.0.54 under Cygwin.  I do this because I
>>> like to keep the same configuration and file system organization to make
>>> my build as portable as possbile under the different Unices I work with.
>>>
>>> I like to compile apache with DSO support and all modules as shared
>>> objects.  The compile seems to work fine but when I do the install all
>>> the modules are named with either an .a or .la extension - I'm expecting
>>> .so.  From various threads I've read there seems to be an issue with
>>> libtool that contributes to this.
...
>> Have you not noticed that apache2 (with .so support) is available as
>> an official Cygwin package through setup.exe ??
...
> Yes I did.  I tried to pick up the source to see how the build was done
> but the source option was not available.

The source is definitely on the mirrors.

> I always build Apache by hand.  See my initial portability comment above.

Wouldn't a few symlinks accomplish the same purpose with much less fuss?

> If push comes to shove I may have to use the official Cygwin port but
> I'd like to be able to just do a ./configure and make like I do on the
> other platforms :)

Patches are necessary to get things building dynamically on Cygwin, so any 
existing build recipe alone won't be enough.

>>> Incidentally mod_php,
>>> and mySQL is next so advice there would be appreciated  too.
>>
>> I've got php5 to compile, but I've got a fair bit of work to do on it
>> before I can release an official package.
>
> When you say you got php to compile did you mean as an Apache module?

Yes.

Max.


--
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/