This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: httpd-2.0.52 (Apache2) testers wanted / maintainer searched


Sorry for comiing in late, I'm currently out of office.

Jon A. Lambert wrote:

Gerrit P. Haase wrote:

Hi,

I just wanted to know if it is possible and if it is running and the
answer is: *yes*. I have Apache2 compiled with a shared core and
shared modules, I offer a full patch and script so you can do the
same with just running the buildscript against the patched sources.


I figured out how to run the patch file. Whee!

$ cd httpd*

/oem-install/httpd-2.0.52 $ patch -p1 -i ../httpd-2.0.52-1.patch
patching file CYGWIN-PATCHES/README
....ellided
patching file srclib/apr/configure.in

Looks good.

---------------
But now how do I run this build-script and from where?
Or should I be running ./configure at this point.

In the source package are three files, the original source, the paptchfile and the script, after extracting the source run:
$ ./httpd-2.0.52-1.sh prep
This extracts the source and aplies the patch
$ ./httpd-2.0.52-1.sh conf
$ ./httpd-2.0.52-1.sh build
$ ./httpd-2.0.52-1.sh install
...


See the bottom of the script, there is an option 'all' which runs
all needed script targets, there are some more eg. 'strip'.
It should work to run
$ ./httpd-2.0.52-1.sh all
which will create a new binary tarball and a new source tarball.


The README indicates you can't build loadable shared objects?
My intention is to use Subversion via mod_svn_dav and Eruby via mod_ruby Does that mean I will have compile the above first into the modules
and then make ./configure link them in the executable?
Does anyone have additional notes, advice or information on Apache2?

There is also a script included in my patch which creates the loadable shared modules. What I have not fixed is the Apache script which is used to build third party extension modules. It should be sufficient to build the modules as static archives, then take a look at the script in the modules directory of the apache source how to create a shared library/module from the static archives. After the module DLL is created, copy it to the modules path and add it in httpd.conf.

However, I saw problems with loading websites greater than 8k.

Gerrit
--
=^..^=

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]