public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tod <tod@madtoon.net>
To: cygwin@cygwin.com
Subject: Compiling Apache2 under Cygwin with .so support
Date: Wed, 28 Sep 2005 14:51:00 -0000	[thread overview]
Message-ID: <433AA6CD.8010505@madtoon.net> (raw)

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.

I tried the -no-undefined LDFLAGS option and the build failed on an 
all-recursive libaprutil-0.la error.

What I'm wondering is if anyone got this to work correctly and if so 
could provide some pointers to get it to work.  Incidentally mod_php, 
and mySQL is next so advice there would be appreciated  too.  In fact if 
there is an up to date CAMP howto document somewhere that would be helpful.


Thanks - Tod
---


uname -rvo - 1.5.18(0.132/4/2) 2005-07-02 20:30 Cygwin
apache v2.0.54
gcc 3.4.4
libtool 1.5.20


--
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-09-28 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 14:51 Tod [this message]
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

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=433AA6CD.8010505@madtoon.net \
    --to=tod@madtoon.net \
    --cc=cygwin@cygwin.com \
    /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).