search for: submak

..._CFLAGS= -Wall" R CMD SHLIB rc.c -o rc.so also works fine. However, MAKEFLAGS="CC=gcc-3.0 PKG_CFLAGS= -Wall -pedantic" R CMD SHLIB rc.c -o rc.so does not work fine. Make throws a fit and spews forth gibberish. My understanding of MAKEFLAGS is that it is for passing flags to some submake process, in this case R CMD SHLIB. The documentation (make manual) says that "Words in the value of `MAKEFLAGS' that contain `=', `make' treats as variable definitions just as if they appeared on the command line." However, there seems to be a problem when the variable defi...

I'm going to want to submit patches for MacOS X in the near future (hopefully tonight or tomorrow night), but I don't see what flags to cvs diff you guys like to receive. Included in these patches will be a MacOS X module for libao which uses the CoreAudio framework along with some other minor stuff. -tim --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project

...L_REPO)/pub/linux/kernel/v$(_LINUX_VDIR)/$(_LINUX_XDIR)/$(@F) -O./$@ + wget $(LINUX_REPO)/$(LINUX_REPO_PATCH_PATH)/$(@F) \ + -O$(DOWNLOAD_DIR)/$@ || { rm -f $(DOWNLOAD_DIR)/$@; false; } pristine-%: pristine-%/.valid-pristine @true + +# unpack-pristine and patch-pristine targets are run in a submake +# so that vpath is re-evaluated. This is important for the case +# where the files are dowloaded this time around, and they are downloaded +# into an alternate directory, as specified by DOWNLOAD_PATH + +unpack-pristine-%-X: % + tar -C $(UNPACK_DIR) -jxf $< + +patch-pristine-%-X: % + echo $&lt...