On Fri, Jul 22, 2011 at 02:38:30PM -0400, Christoph Hellwig wrote: > > You can get most of this by simply using make V=1, not just in xfsprogs, > but in most projects using silent make output (including those using > automake) Yeah, I know about V=1 (and I have been using it), but I wanted to know which of the many Makefile variables which finally make up $(CFLAGS) was getting set to which value, and V=1 doesn't do this. > for me. The biggest thing is that you have another directory in your > include path. How did you add that one? Did you add anything else > special to the ./configure or make command lines? Yes I needed it because I wanted to do a hermetic build; that is, I didn't want to depend on the version of the acl, attr, dmapi, etc., shipped by the distribution. (This is actually more important when building xfstests, since I wanted to make sure we used the version of the xfsprogs headers shipped by the very tip of xfsprogs-dev, since in the past I've had problems because the distro-shipped header files were too old.) The way I did that was by setting the environment CFLAGS to -I/kbuild/xfstests/bld/include. And that seems to be the problem. If CFLAGS is set as an environment variable, then it's set as a :=, which means that CFLAGS is set right away, the first time buildmacros is included. How about this instead? A patch like this so that CFLAGS can be remembered at configure time: diff --git a/include/builddefs.in b/include/builddefs.in index 4c8ec64..81ebfcd 100644 --- a/include/builddefs.in +++ b/include/builddefs.in @@ -25,6 +25,7 @@ OPTIMIZER = @opt_build@ MALLOCLIB = @malloc_lib@ LOADERFLAGS = @LDFLAGS@ LTLDFLAGS = @LDFLAGS@ +CFLAGS = @CFLAGS@ LIBRT = @librt@ LIBUUID = @libuuid@ Then I don't have to set an environment variable when running make; I just have to pass it to configure. - Ted _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
