Benoit SIGOURE <[EMAIL PROTECTED]> writes:
> How shall I proceed, is there a test suite I can run against newlib to
> check for missing functions or something? Or shall I simply hack a
> script that builds up one test per function mentioned in gnulib?
Run
gnulib-tool --create-megatestdir --dir ~/some/where/
and wait for it to finish, then run ./configure && make check in
~/some/where/.
Actually, it would be interesting to see how many common (and not so
common) platforms trigger each gnulib module to become enabled. I'm
thinking a matrix:
Debian GNU/Linux Windows XP MinGW Mac OS X
i386-linux-gnu i586-mingw32msvc-gnu powerpc-... ....
malloc: no yes yes
argp: no no yes
strerror: yes yes yes
etc.
This would make it simpler to find where the gnulib m4 test is incorrect
and trigger enabling of gnulib modules where it may not actually be
needed. Now we are relying on people to notice this manually.
Hm.
/Simon
