note 33052 deleted from internals2.ze1.zendapi by cmb

Note Submitter: wilf at bigpond dot net dot au ---- Another caching problem: If you seen a message saying that 'may contain buggy cache code', ensure that you delete the 'autom4k...cache' directory before running buildconf. A good test the see if your new module has been picked up by buildconf is: $ grep -c my_module configure (if that returns 0 then buildconf did not work). Unfortunately this means that you have to completely rebuild your configure script each time you change an M4 file but it doesnt take too long.