Jeff Trawick wrote:
Ken's talking binbuild...
For what we distribute, certainly. But I think static
libraries should also be our default. Otherwise someone
who builds from scratch is going to run into the same
astonishment when it tries to copies home-built files
around. It'll look like it
On Tue, Jan 29, 2002 at 09:00:06PM -0500, Rodent of Unusual Size wrote:
httpd, htpasswd, htdigest, and the other main applications need
to be built with static libraries. In other words, they must
not be linked against libapr.so and friends.
Why? Because otherwise we make life difficult
On Wed, Jan 30, 2002 at 07:43:36AM -0800, Aaron Bannert wrote:
I've already added this for our various support binaries:
--enable-static-htpasswd
...
I see no reason why we couldn't do the same for httpd. I agree that it
may make life easier for binbuild users, but I'm totally against
Aaron Bannert wrote:
On Tue, Jan 29, 2002 at 09:00:06PM -0500, Rodent of Unusual Size wrote:
httpd, htpasswd, htdigest, and the other main applications need
to be built with static libraries. In other words, they must
not be linked against libapr.so and friends.
Why? Because
On Wed, Jan 30, 2002 at 11:30:23AM -0500, Greg Ames wrote:
I see no reason why we couldn't do the same for httpd. I agree that it
may make life easier for binbuild users,
that would be most excellent
but I'm totally against doing
this
Aaron Bannert wrote:
I've already added this for our various support binaries:
--enable-static-htpasswd
Having to explicitly specify this to make it happen is not on;
it needs to be the default. Having to specify for each individual
util is also bogus; there should be a switch, defaulting
Aaron Bannert wrote:
I tried sticking --disable-shared for apr and apr-util in httpd's configure.in.
That doesn't work any more if you try to build the modules shared.
I think all you have to do is pass -static to the libtool link command
for httpd. I'll be able to fool around with this
On Wed, Jan 30, 2002 at 12:00:23PM -0500, Rodent of Unusual Size wrote:
Aaron Bannert wrote:
I've already added this for our various support binaries:
--enable-static-htpasswd
Having to explicitly specify this to make it happen is not on;
it needs to be the default. Having to specify
On Wed, Jan 30, 2002 at 01:20:49PM -0600, William A. Rowe, Jr. wrote:
Certainly would agree there. httpd has dozens of modules loading anyways,
and benefits greatly from the apachectl configuration of the DYLD path,
etc. Even linking httpd static causes headaches for dynamic modules, when
Aaron Bannert [EMAIL PROTECTED] writes:
On Wed, Jan 30, 2002 at 12:00:23PM -0500, Rodent of Unusual Size wrote:
Aaron Bannert wrote:
I've already added this for our various support binaries:
--enable-static-htpasswd
Having to explicitly specify this to make it happen is not on;
Justin Erenkrantz wrote:
On Wed, Jan 30, 2002 at 01:20:49PM -0600, William A. Rowe, Jr. wrote:
Certainly would agree there. httpd has dozens of modules loading anyways,
and benefits greatly from the apachectl configuration of the DYLD path,
etc. Even linking httpd static causes
httpd, htpasswd, htdigest, and the other main applications need
to be built with static libraries. In other words, they must
not be linked against libapr.so and friends.
Why? Because otherwise we make life difficult for users, and
make violation of the Principle of Least Astonishment a virtual
Rodent of Unusual Size [EMAIL PROTECTED] writes:
httpd, htpasswd, htdigest, and the other main applications need
to be built with static libraries. In other words, they must
not be linked against libapr.so and friends.
Why? Because otherwise we make life difficult for users, and
make
13 matches
Mail list logo
