On Sat, Jan 21, 2006 at 01:52:33PM -0200, Henrique de Moraes Holschuh wrote: > On Fri, 20 Jan 2006, Michael Banck wrote: > > ++#include <config.h> > > Shouldn't it be "config.h" or (if the build system is not doing things > right, "<relativepath>/config.h") ?
Well, I think I wondered as well when I first saw the patch, but: nighthawk~/build/chroot-unstable/build/mbanck/cyrus-sasl2-2.1.19/build-tree/cyrus-sasl-2.1.19$ grep -R ^\#include.*config\.h * lib/getaddrinfo.c:#include "config.h" lib/getnameinfo.c:#include "config.h" lib/snprintf.c:#include <config.h> lib/auxprop.c:#include <config.h> lib/canonusr.c:#include <config.h> lib/checkpw.c:#include <config.h> lib/client.c:#include <config.h> lib/common.c:#include <config.h> lib/external.c:#include <config.h> lib/md5.c:#include <config.h> lib/saslutil.c:#include <config.h> lib/server.c:#include <config.h> lib/seterror.c:#include <config.h> lib/dlopen.c:#include <config.h> lib/saslint.h:#include <config.h> lib/windlopen.c:#include <config.h> so it seems consistent with the rest of the source, at least the parts in lib/. Michael -- Michael Banck Debian Developer [EMAIL PROTECTED] http://www.advogato.org/person/mbanck/diary.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
