module name differences depending on how generated

[Skip Montanaro]

    Richard> The problem I then had was that in patching nismodule.c to fix
    Richard> a documented problem in the nismdoule.c code running under
    Richard> Linux running make install to generate a revised nis support
    Richard> module produced and installed a new nismodule.so. But this had
    Richard> no effect as the originally generated nis.so was being picked
    Richard> up in preference. Of course nis.so was not being regenerated
    Richard> and installed (presumably because setup.py detected that
    Richard> nismodule.so was being produced) so that at first blush the
    Richard> patch appeared to be ineffective.

At the moment, setup.py doesn't do a good job of deducing dependencies.  You
will have to manually delete the nismodule.o and nis.so files to get them to
rebuild.

-- 
Skip Montanaro (skip at pobox.com - http://www.mojam.com/)
Boycott Netflix - they spam - http://www.musi-cal.com/~skip/netflix.html