Max Horn wrote: > Yes yes, I do fully agree it would be a nice thing to have (and it was > discussed a bit in the past). > > I am now more wondering, how would it be done exactly.
I checked out the make manual and it has a --warn-undefined-variables switch. I tried that out on openjade and it reported: Makefile:76: warning: undefined variable `XLIBDIRS' Makefile:33: warning: undefined variable `libdir' Makefile:76: warning: undefined variable `XLIBDIRS' ./../Makefile.comm:40: warning: undefined variable `DEBUG' When building properly (naturally it doesn't help until *after* I know what the problem is :-/). It would be nice if there were a way for it to report exactly which environment variables it is dependent on, but at least this can be used by package maintainers to verify that they are not depending on unset variables in their environment. jim ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
