| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management) Resent-To: gnats-admin@rt-11.MIT.EDU Resent-Reply-To: krb5-bugs@MIT.EDU, Greg Hudson <ghudson@MIT.EDU> Date: Wed, 16 Dec 1998 21:29:23 -0500 (EST) From: Greg Hudson <ghudson@MIT.EDU> To: krb5-bugs@MIT.EDU >Number: 677 >Category: pending >Synopsis: Build system problems >Confidential: yes >Severity: serious >Priority: medium >Responsible: gnats-admin >State: open >Class: sw-bug >Submitter-Id: unknown >Arrival-Date: Wed Dec 16 21:30:00 EST 1998 >Last-Modified: >Originator: >Organization: >Release: >Environment: >Description: >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: Here are two problems with the krb5 build system: * 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). * When you have required preprocessor flags like -I../include and -L../lib, they should go on the command line before anything the user might have specified. If I tell the build system I want -L/usr/athena/lib in my link lines, krb5 should not put that first and pick up previously installed krb5 libraries from there.
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |