... which prevents its use when needed (for groff, etc.) Is there any (automated?) way to determine what modules are required for a given OS? At the very least, IRIX needs: + *-irix*) + requested_gnulib_modules="getopt" + ;;
In bug#264266 there is some incomplete test script for a list of modules to start with. More modules are to be added when needed.
According to the test from Bug 264266, IRIX (6.5.x) requires: alphasort dirfd getopt scandir strcasestr strndup xvasprintf ... although there are system manpages for alphasort (dirent.h), dirfd (sys/dir.h), and scandir (dirent.h), so these may not be required.
Starting with gnulib modules 'getopt strcasestr strndup xvasprintf' for irix in r48470. ATM I can see app-arch/unrar-gpl, app-cdr/cuetools, app-misc/pax-utils, app-portage/euses, app-portage/portage-utils making use of gnulib. IIRC it was app-portage/portage-utils needing many of them, but recent versions might need less.
I notice that gnulib installs into "${EPREFIX}/usr/$(get_libdir)/gnulib/$(get_libdir)/" - is this intended?
IRIX also requires that (at least) sys-apps/groff (Bug 277041) and media-libs/speex (Bug 267854) also use gnulib, due to getopt_long.
(In reply to comment #4) > I notice that gnulib installs into > "${EPREFIX}/usr/$(get_libdir)/gnulib/$(get_libdir)/" - is this intended? Yes. The header files partially override headers in ${EPREFIX}/usr/include/. And the library should not be found by accident.
I was wondering about "${EPREFIX}/usr/$(get_libdir)/gnulib/$(get_libdir)/" versus "${EPREFIX}/usr/$(get_libdir)/gnulib/lib/" - the second $(get_libdir) seems superfluous, and I was wondering if it was a quirk of my installation.
Indeed, this might not be necessary. While get_libdir basically is irrelevant in Prefix anyway, I'm unsure if dropping the second one can work in theory when (some of) /usr/lib* is symlinked.
