GNOME Bugzilla – Bug 339923
Makefile.in.in contains SHELL=/bin/sh but uses bashisms
Last modified: 2006-04-27 16:26:10 UTC
Makefile.in.in sets SHELL to /bin/sh, but then uses bashisms, causing cosmetic errors on Solaris where /bin/sh is the original Bourne shell. This can be seen in http://jhbuild.bxlug.be/builds/2006-04-27-0002/logs/system-tools-backends/#build (also in #check, but the xgettext errors are a separate bug due to /usr/bin/xgettext not being GNU xgettext, although I'm not sure what to file it on).
The bashisms are a duplicate bug, and the test -e was already fixed. If you can tell me exactly what is wrong, that causes the unexpected EOF, I am happy to fix them. We can't specify SHELL = /bin/bash here either, as the install location of bash is not guaranteed across systems. As for supporting solaris gettext, it isn't happening. The overwhelming number of features and improvements that GNU gettext has over solaris gettext is not worth trying to work around not having. We use a large number of the command line options for GNU xgettext which just don't exist in any form on Solaris. This is discussed in bug #301364 where we agree to just require GNU gettext. However, the bug is still open, as I've not had time to go through and fix intltool to check that GNU gettext is being used, everywhere it calls the gettext programs. *** This bug has been marked as a duplicate of 339770 ***