I like the idea of statically linking apr/apr-util to httpd. Just not sure how that impacts DSOs that need APR functions.
How 'bout creating a script in bin, setupenvars.bat than folks need to learn to run before issuing httpd -yadda? Not pretty but very straight forward... Bill ----- Original Message ----- From: "Jeff Trawick" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 26, 2002 10:55 AM Subject: more fun with binary builds (showstoppers?) > 1) $prefix isn't getting fixed-up by install-bindist.sh, at least on > Solaris > > 2) where is the build directory? we need some stuff like > config_vars.mk > > 3) a cool problem you'll run into after fixing the above > > download a binary build > install it > run apxs > ouch! > > apxs doesn't pick up the environment variable needed to find libapr, > libaprutil, libexpat, so "httpd -l" bombs... > > cool, huh? > > some possible solutions: > > just link those libraries statically to httpd and save ourselves > certain types of grief (but probably bring on other types of grief > which I don't really understand) > > add an apachectl option to let you pass whatever you want to httpd; > if apxs uses apachectl, it will pick up any envvars needed to find > the libraries > > have apachectl parse the envvars file and set whatever is necessary > before calling httpd (gross) > > have apachectl create a temporary /bin/sh script which sources > envvars and then does httpd -l (still fairly gross) > > have apxs know what OS-specific variable to set to find the > libraries > > -- > Jeff Trawick | [EMAIL PROTECTED] > Born in Roswell... married an alien... >
