public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tod <tod@madtoon.net>
To: Max Bowsher <maxb@ukf.net>
Cc: Cygwin <cygwin@cygwin.com>
Subject: Re: Compiling Apache2 under Cygwin with .so support
Date: Wed, 05 Oct 2005 16:58:00 -0000	[thread overview]
Message-ID: <4344010A.1030205@madtoon.net> (raw)
In-Reply-To: <072801c5c46c$5a2dcbf0$5304a8c0@chimaera>

Max Bowsher wrote:

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

Sorry,  I normally do.

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

Ok, I'll look again.


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

Will the source from one of the mirrors have the necessary components to 
accomplish that?  If not, is there a step by step set of instructions 
published anywhere?

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

Great, what else needs to be done?

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

      reply	other threads:[~2005-10-05 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 14:51 Tod
2005-09-28 18:14 ` Max Bowsher
     [not found]   ` <433AD19A.4000208@madtoon.net>
2005-09-28 22:19     ` Max Bowsher
2005-10-05 16:58       ` Tod [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4344010A.1030205@madtoon.net \
    --to=tod@madtoon.net \
    --cc=cygwin@cygwin.com \
    --cc=maxb@ukf.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).