Well, just slightly confused. On my system I have "tested" in as much as I can https://hostname and it says "It works!". What I need some assistence with perhaps is determeing which "mpm" binary was built, as I am only building one with 2.2.22 at the moment.
re: Having only one script - I am not surprised there must be more than one, but I hoped :) There are actually two scripts - one that does the configure/make/make install, and one that creates the template needed to make the package. FYI: I am working on getting a build for a svn client as well. AND - I am doing these things because I am very tired of having to download 10 to 20 .rpm packages, each with moving dependancies it seems, in order to install something that is supposed readily available. In short, I am trying to make some packages that just 'install' with saying - you need this too, and then when you install that - it says and I need this first, etc etc. In a word, boring. FYI: current tools (IBM and others) use /opt/freeware as their main installation area - so I am opting for /opt/* (no freeware in the name) for packages like coreutils, libz, pcre, apr, apr-util, etc. and applications (packaging) such as httpd and svn in /opt/httpd, /opt/svn. With your wealth of prior experience - if you see a trap I am setting for myself, please warn me - and better - lead me to safety. regards, Michael On Wed, Feb 8, 2012 at 3:40 PM, Jeff Trawick <[email protected]> wrote: > On Wed, Feb 8, 2012 at 9:08 AM, Michael Felt <[email protected]> wrote: > > Well, it was building "something". I'll try the proposed change and make > > sure it is still giving me "all" the mods. > > yeah, that was the idea... thanks! > > > FYI - I have added --enable-ssl (so that the same script works for both > > 2.2.22 and 2.4.0 which have different ideas of "all". > > As Graham mentioned, expect to have different scripts for different > releases and do the right thing for each release. It isn't a good > thing if people who play with configure more often but might not know > the ancient history stare at the script and wonder about the odd > choice of arguments. (I happen to remember about the AIX/--enable-so > issue from long ago, but that needs to die.) > > > And I hope configure will still leave AIX modules as shared (as it used > to > > make them all static by default - long ago). > > If it doesn't build them shared using the appropriate configure args, > that's what needs to be fixed. (Most people won't use this script.) > > > > > I shall try both 2.4.0 and 2.2.22 (without --enable-ssl) - and I am > > continuing to work towards to havin g APR external to httpd. > > > > > > On Tue, Feb 7, 2012 at 8:09 PM, Jeff Trawick <[email protected]> wrote: > >> > >> The buildaix.ksh script committed recently had some outdated options > >> or requirements, and didn't build loadable MPMs. Suggested changes > >> are below. Do or do not fold, spindle, or mutilate; commit with or > >> without testing; etc. > >> > >> Index: build/aix/buildaix.ksh > >> =================================================================== > >> --- build/aix/buildaix.ksh (revision 1241549) > >> +++ build/aix/buildaix.ksh (working copy) > >> @@ -30,11 +30,7 @@ > >> > nohup.out > >> ./configure \ > >> --enable-layout=$LAYOUT \ > >> - --enable-module=so \ > >> - --enable-proxy \ > >> - --enable-cache \ > >> - --enable-disk-cache \ > >> - --with-mpm=worker \ > >> + --enable-mpms-shared=all \ > >> --enable-mods-shared=all | tee nohup.out > >> > >> make | tee -a nohup.out > >> > >> -- > >> Born in Roswell... married an alien... > > > > > > > > -- > Born in Roswell... married an alien... >
