Hi Helmut, > If yes, what would be a good check? Should it just check the toplevel > configure.ac and configure.in or any file found on any directory level?
This is my primary concern — warning about broken configure.{am,in} in code copies etc. that are not used would just be annoying. It might be safe to simply check ./configure.{am,in} or perhaps a hardcoded list of subdirs such as src/configure.{am,in}. What do you think? > I haven't performed a whole archive-analysis yet, so I cannot tell > about the amount of fpos to be expected. Would this be easy for you to do? Please go ahead if so and let us know. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-