Mailing List Archive

rse 98/05/04 07:44:36

Modified: src Configuration.tmpl
Log:
Some enhancements to the comments:

- give hint where compiler and optimization flags have to
specified (under CC and OPTIM)

- give hint that using -O3 (or -O6 which is used often for pgcc) is risky

- remove example from out-commented entry because this is
inconsistent with the other entries and only leads to less
thinking by the user

Feel free to fix me here.

Revision Changes Path
1.102 +10 -4 apache-1.3/src/Configuration.tmpl

Index: Configuration.tmpl
===================================================================
RCS file: /export/home/cvs/apache-1.3/src/Configuration.tmpl,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -r1.101 -r1.102
--- Configuration.tmpl 1998/04/27 08:17:25 1.101
+++ Configuration.tmpl 1998/05/04 14:44:36 1.102
@@ -37,17 +37,23 @@
# will be added to whatever flags Configure determines as appropriate
# and needed for your platform.
#
-# You can also set the compiler and Optimization used here as well.
-# Settings here have priority; If not set, Configure will attempt to guess
-# the C compiler, looking for gcc first, then cc.
+# You can also set the compiler (CC) and optimization (OPTIM) used here as
+# well. Settings here have priority; If not set, Configure will attempt to
+# guess the C compiler, looking for gcc first, then cc.
#
+# Optimization note:
+# Be careful when adding optimization flags (like -O3 or -O6) on the OPTIM
+# entry, especially when using some GCC variants. Experience showed that using
+# these for compiling Apache is risky. If you don't want to see Apache dumping
+# core regularly then at most use -O or -O2.
+#
EXTRA_CFLAGS=
EXTRA_LDFLAGS=
EXTRA_LIBS=
EXTRA_INCLUDES=

#CC=
-#OPTIM=-O2
+#OPTIM=
#RANLIB=

################################################################