www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Erenkrantz <jerenkra...@ebuilt.com>
Subject Re: build/9955: libtool: link: `/usr/local/lib/libexpat.la' is not a valid libtool archive
Date Fri, 01 Mar 2002 08:25:44 GMT
On Fri, Mar 01, 2002 at 03:14:23AM +0000, Philip M. Gollucci wrote:
> Sorry about this... its my fault... I neglected to mention, that it
> happens anwywhere in the code that libexpat.la is used.
> The changes for the apr-util  worked fine.  If you make the
> same changes for the following additional files, I think all will be well.
> [See bottom for list.]
> If you would like make output, let me know.  I would go through and make
> the same changes you made to apu-conf.m4 myself, but looking at the pcre
> directory, it might be a little harder for me to find.

I'm not sure what you are saying here - is it fixed or not with
my latest commits?

Once you patch apu-conf.m4, run buildconf, and re-run configure, all
should be well.  Is that not what you are seeing?  I'm not sure how
pcre fits in - if there are any references to libexpat.la, it is
indirectly coming from apr-util's value.

> If your interested, I actually have 2.0.32 up and running on FBSD4.5 on
> port 9595 (the one where I manually link libexpat.a where it fails)
> One small problem with this though... apachectl script has the path to
> httpd wrong in apachectl.in
> Heres a patch that fixes this:
> [ttyp4]:philip@p6m7g8.student.umd.edu
> /usr/home/src/apache/httpd-2.0/support 310 >diff -u apachectl-old.in
> apachectl.in
> --- apachectl-old.in    Fri Mar  1 03:03:23 2002
> +++ apachectl.in        Fri Mar  1 03:03:15 2002
> @@ -29,7 +29,7 @@
>  PIDFILE=@prefix@/logs/@progname@.pid
>  #
>  # the path to your httpd binary, including options if necessary
> -HTTPD='@prefix@/bin/@progname@'
> +HTTPD='@prefix@/sbin/@progname@'
>  #
>  # pick up any necessary environment variables
>  if test -f @prefix@/bin/envvars; then

I don't know if you track dev@httpd, but our current CVS 
repository has busted installation paths.  And, FWIW, that should
be ${bindir} anyway.  I'll point it out to Aaron and Thom
tomorrow.  -- justin

View raw message