Re: cvs commit

> Oh, my apologies, I didn't realize config.h.in was a generated file (I'm > still fairly new to autoconf). I guess I figured it was the *.in files you > edited. I didn't count of two levels of file generation..... The problem is that config.h.in shouldn't be under CVS control since it's generated on the client side (much as configure) Simply don't care about it - if you add something to configure.in, run autoheader afterwards, see if you need to add something to acconfig.h, run autoheader again and commit your changes (including config.h.in). -- Regards, Sascha Schumann Consultant