[3021] in Kerberos-V5-bugs
Re: pending/677: Build system problems
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Thu Dec 17 12:44:34 1998
Date: Thu, 17 Dec 1998 12:44:11 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: krb5-bugs@MIT.EDU, Greg Hudson <ghudson@MIT.EDU>
Cc: gnats-admin@RT-11.MIT.EDU, krb5-prs@RT-11.MIT.EDU
In-Reply-To: Greg Hudson's message of Wed, 16 Dec 1998 21:30:01 -0500,
<199812170230.VAA11040@rt-11.MIT.EDU>
* The user should be able to run "make CFLAGS=foo" to override
the non-required cflags (-g vs. -O and anything specified in
the CFLAGS environment variable at configure time) for the
program. The same applies to CPPFLAGS and LDFLAGS. krb5
uses CFLAGS and LDFLAGS as its own variables, stuffing
things like the -I../include options which are required for
compilation. This violates the gnu makefile standards, and
means that I can't control the compilation of krb5 in the
same way I control the compilation of other autoconf'd
packages (by putting LDFLAGS and CPPFLAGS or CFLAGS
declarations in config.site).
Use the --with-ccflags option to the configure script instead. IMHO, the
GNU Makefile standards are broken, since you can do the configure tests
with one set of CFLAGS options, and then compile with a different set of
CFLAGS options. It's also extremely inconvenient as a developer to
type "make CFLAGS=foo" each time I recompile in a particular directory,
instead of simply running "configure --with-cflags=foo" once, and then
simply typing "make" when I need to recompile in a particular directory.
Yes, at some point I suppose I should make CFLAGS work the way folks
used to GNU conventions work, but for now, the easiest workaround is to
use --with-ccflags option.
- Ted
