> Another approach would be to ask kbuild for > this information so we do not expose various filenames to the > outer world. For shell scripts and makefiles, running a command like make and retrieving its output via pipe is de rigueur. But for some other programs it might be substantially less hassle to just read plain files. That's what I was thinking, anyway. (I only really think that $ARCH is something that anyone would want to fetch before they'd run make anyway, and I guess $SUBARCH in the case of ARCH=um, but not $CROSS_COMPILE.) > This is analogous to the way we ask for > kernelrelease and kernelversion these days. Except that include/config/kernel.release is there for all to see (when referring to /lib/modules/.../build directory, e.g.), so perhaps some people are in fact using that. Thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
