I've been working on a kernel module package that builds on multiple distros (SLES9, SLES 10, openSUSE, RHEL, Fedora, etc.). I looked at the kernel module packages on the Build Service for some guidance, did some digging, etc. I finally came upon something that worked fine on a non-buildservice machine. In fact, it builds find on an actual <foo linux> install, but not so much with the build service. In particular, SLES 10. The 'offending' parts from the spec file are along the lines of: ******* for flavor in %{flavors_to_build}; do rm -rf obj/$flavor cp -r source obj/$flavor make -C %kernel_source $flavor ${MODULES_CONF_PARAMS} \ M=$PWD/obj/$flavor/ \ modules done ******* I receive an error to the extent of: ******* + make -C %kernel_source '%{flavors_to_build}' make: *** %kernel_source: No such file or directory. Stop. error: Bad exit status from /var/tmp/rpm-tmp.25150 (%build) ******* In the SuSE RPM Macros, %kernel_source is defined as part of the %_kernel_module_package macro (which is itself called by %suse_kernel_module_package). For that matter, so is %{flavors_to_build}. Since I'm calling %_kernel_module_package without a problem, why aren't some of the other values it defines available? The macros are installed as part of the 'rpm' package on SLES 10, which the log shows is installed. (And I'm aware on other distros it's released elsewhere...) When I run the RPM creation command from a SLES 10 box, it builds fine. Any ideas? -- Troy Telford --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org