You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Gonyou, Austin" <au...@coremetrics.com> on 2001/08/08 23:16:33 UTC
apr-util/buildconf.sh patch
Here is a patch for buildconf that gets rid of the erronious messages that
the system libtool (using 1.4) outputs:
--------snip--------
--- buildconf.sh.old Wed Aug 8 16:05:01 2001
+++ buildconf.sh Wed Aug 8 16:06:10 2001
@@ -21,8 +21,9 @@
#
# Note: we always replace the files, and we copy (rather than link) them.
#
-echo "Copying libtool helper files ..."
-$libtoolize --force --copy
+#Per RBB this is not needed anymore, so removing.
+#echo "Copying libtool helper files ..."
+#$libtoolize --force --copy
#
# Generate the autoconf header (include/apu_config.h) and ./configure
--------snip--------
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com
Re: apr-util/buildconf.sh patch
Posted by Ryan Bloom <rb...@covalent.net>.
On Wednesday 08 August 2001 14:35, Justin Erenkrantz wrote:
> On Wed, Aug 08, 2001 at 02:32:33PM -0700, Ryan Bloom wrote:
> > In that case, can we delete the buildconf.sh file?
>
> I already did. Your local CVS client may not have removed it perhaps?
>
> cvs log buildconf.sh
> revision 1.12
> date: 2001/08/01 20:47:12; author: jerenkrantz; state: dead; lines: +0
> -0
>
> You shouldn't have it locally... -- justin
I don't. I'm wondering why Austin does though.
Ryan
--
_____________________________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
-----------------------------------------------------------------------------
Re: apr-util/buildconf.sh patch
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Wed, Aug 08, 2001 at 02:32:33PM -0700, Ryan Bloom wrote:
>
> In that case, can we delete the buildconf.sh file?
I already did. Your local CVS client may not have removed it perhaps?
cvs log buildconf.sh
revision 1.12
date: 2001/08/01 20:47:12; author: jerenkrantz; state: dead; lines: +0 -0
You shouldn't have it locally... -- justin
Re: apr-util/buildconf.sh patch
Posted by Ryan Bloom <rb...@covalent.net>.
In that case, can we delete the buildconf.sh file?
Ryan
On Wednesday 08 August 2001 14:23, Justin Erenkrantz wrote:
> On Wed, Aug 08, 2001 at 04:16:33PM -0500, Gonyou, Austin wrote:
> > Here is a patch for buildconf that gets rid of the erronious messages
> > that the system libtool (using 1.4) outputs:
>
> buildconf.sh is no longer valid in apr-util - you should be using
> buildconf.
>
> When I renamed it from buildconf.sh, I took out most of the libtool
> generation code (including that line). However, the configure.in
> for apr-util includes the libtool.m4 in apr. Commit coming for
> that, but that doesn't harm anything. -- justin
--
_____________________________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
-----------------------------------------------------------------------------
Re: apr-util/buildconf.sh patch
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Wed, Aug 08, 2001 at 04:16:33PM -0500, Gonyou, Austin wrote:
> Here is a patch for buildconf that gets rid of the erronious messages that
> the system libtool (using 1.4) outputs:
buildconf.sh is no longer valid in apr-util - you should be using
buildconf.
When I renamed it from buildconf.sh, I took out most of the libtool
generation code (including that line). However, the configure.in
for apr-util includes the libtool.m4 in apr. Commit coming for
that, but that doesn't harm anything. -- justin