Jarno Rajahalme wrote: > thought I have a problem with gnulib, so I did make distclean, git pull on > gnulib, gnulib-tool --import, ./configure.
After the gnulib-tool invocation, you likely need to insert an 'autoreconf' invocation. Often it may work without it, but not always. > I have now these defined in config.h, after doing the above: > > #define NEED_PRINTF_DIRECTIVE_A 1 > ... > m4/gnulib-cache looks like this: > > gl_LOCAL_DIR([gl]) > gl_MODULES([ > ... > round > roundf > ... > vsnprintf > ]) Yup, this is pretty much the situation that I imagined. Probably the patch that I've just committed will fix it. > running "gnulib-tool --create-megatestdir --with-tests --dir=..." completes. > Yesterday it failed to complete, and today it has been running for about 5 > hours already, is this normal? Yes. The "megatestdir" is really huge, as the name says. It is the right tool for testing the completeness of the dependencies of a single module, but a situation where two specific modules combined (like here, 'round' and 'vsnprintf') will not be detected even by the megatestdir. For testing portability, one usually uses the --create-testdir option. Bruno
