Bug#426561: modpost wrapper fails if given no filenames

[Ben Hutchings <bhutchings@solarflare.com>]

Package: linux-kbuild-2.6.18
Version: 2.6.18-1

If a module source directory does not provide source for any complete
modules, "stage 2" of the build runs modpost with no filenames.  The
upstream version of modpost silently does nothing in this case (so
far as I can see).  Debian's wrapper unconditionally uses the first
non-option argument as a filename, but if there are no such arguments
it uses a null pointer and fails.

This prevents some of our drivers from building on etch, though we
can work around it.

I think the wrapper should be compatible and do nothing if given no
non-option arguments.

Ben.