Markus Krause wrote:
the only obvious difference i could make out is a difference in CFLAGS:
* in freeradius-1.1.3.tar.gz: CFLAGS = $(INCLUDE) -g -O2 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -DDARWIN -Wall -D_GNU_SOURCE -DNDEBUG
* in todays cvs version: CFLAGS = $(INCLUDE) -g -O2 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -DDARWIN -Wall -D_GNU_SOURCE -g -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -W -Wredundant-decls -Wundef
has this been fixed in cvs again already? or am i messing something up?
When you build FreeRADIUS from a CVS snapshot, the ./configure script automatically adds the option --enable-developer for you. That would explain why the CFLAGS are different. See the following excerpt from configure.in (line 286) if test "x$developer" != "xno" -a -d $srcdir/CVS; then dnl turn on the developer flag when taken from a CVS checkout (not a release) developer="yes" fi -- Nicolas Baradakis