You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by be...@hyperreal.org on 1999/12/19 17:36:19 UTC
cvs commit: apache-2.0/src buildconf
ben 99/12/19 08:36:19
Modified: src buildconf
Log:
Build APR, too.
Revision Changes Path
1.2 +25 -0 apache-2.0/src/buildconf
Index: buildconf
===================================================================
RCS file: /export/home/cvs/apache-2.0/src/buildconf,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- buildconf 1999/11/29 23:44:50 1.1
+++ buildconf 1999/12/19 16:36:19 1.2
@@ -105,3 +105,28 @@
echo "buildconf: created or modified configure"
fi
+# Now do APR...
+
+echo "buildconf: setting up APR"
+
+cd lib/apr
+
+mv configure configure.old 2>/dev/null
+autoconf
+if cmp configure.old configure > /dev/null 2>&1; then
+ echo "buildconf: keeping configure"
+ mv configure.old configure
+else
+ echo "buildconf: created or modified configure"
+fi
+
+cd ../..
+
+# Now run the configs...
+
+rm config.cache
+./configure
+
+cd lib/apr
+rm config.cache
+./configure
Re: cvs commit: apache-2.0/src buildconf
Posted by Manoj Kasichainula <ma...@io.com>.
On Sun, Dec 19, 1999 at 04:36:19PM -0000, ben@hyperreal.org wrote:
> +# Now run the configs...
> +
> +rm config.cache
> +./configure
> +
> +cd lib/apr
> +rm config.cache
> +./configure
I think it's best not to do this in buildconf. First of all, there are
lots of options that Apache's configure will want; putting this in
buildconf breaks that. Also, buildconf (or whatever it gets replaced
with) will be one of the steps of building a distribution, so it
shouldn't be running configure.
Any good reason not to take this back out?
--
Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manojk/
"if it ain't broke, break it." -- Ray Brune