[tlbuild] hpux, xetex

[Olaf Weber]

Karl Berry writes:

>             for f in $(SOMEVAR) ; do
> Thanks Arthur.

> So it would seem the answer is to change the Makefiles like this:
> test -z "$(SOMEVAR)" || for f in ...

Actually, the technique below is what we use in other places in the
source, and almost certainly what should be done here.


Index: libs/icu-xetex/data/Makefile.in
===================================================================
--- libs/icu-xetex/data/Makefile.in	(revision 8164)
+++ libs/icu-xetex/data/Makefile.in	(working copy)
@@ -454,7 +454,7 @@
 	echo "// Warning this file is automatically generated" > $@; \
 	echo "$(INDEX_NAME):table(nofallback) {" >> $@; \
 	echo "    InstalledLocales {" >> $@; \
-	for file in $(INSTALLED_COL_FILES); do \
+	for file in ""$(INSTALLED_COL_FILES); do \
 	  echo "        $$file {\"\"}" >> $@; \
 	done; \
 	echo "    }" >> $@; \
@@ -473,7 +473,7 @@
 	echo "// Warning this file is automatically generated" > $@; \
 	echo "$(INDEX_NAME):table(nofallback) {" >> $@; \
 	echo "    InstalledLocales {" >> $@; \
-	for file in $(INSTALLED_BRS_FILES); do \
+	for file in ""$(INSTALLED_BRS_FILES); do \
 	  echo "        $$file {\"\"}" >> $@; \
 	done; \
 	echo "    }" >> $@; \
@@ -492,7 +492,7 @@
 	echo "// Warning this file is automatically generated" > $@; \
 	echo "$(INDEX_NAME):table(nofallback) {" >> $@; \
 	echo "    InstalledLocales {" >> $@; \
-	for file in $(INSTALLED_RBNF_FILES); do \
+	for file in ""$(INSTALLED_RBNF_FILES); do \
 	  echo "        $$file {\"\"}" >> $@; \
 	done; \
 	echo "    }" >> $@; \
@@ -543,7 +543,7 @@
 	echo "$(INDEX_NAME):table(nofallback) {" >> $@; \
         echo "    CLDRVersion { \"$(GENRB_CLDR_VERSION)\" }" >> $@; \
 	echo "    InstalledLocales {" >> $@; \
-	for file in $(INSTALLED_RB_FILES); do \
+	for file in ""$(INSTALLED_RB_FILES); do \
 	  echo "        $$file {\"\"}" >> $@; \
 	done; \
 	echo "    }" >> $@; \


> On other fronts, for background:

> It is intentional and desirable that the SHELL envvar is not respected
> by make, precisely because of users who use [t]csh or whatever.

> Our configure does not, to my recollection, attempt to find the "best"
> shell on a system (whatever that might be).  It always uses /bin/sh.
> (See make/common.mk.)  It is not that hard to write Makefile rules to
> work with every system's /bin/sh, and that's what we have always done.
> (For GNU packages too, almost always.)  Especially now that we don't
> have to deal with Ultrix

> If you want to read about shell portability, try
> http://www.gnu.org/software/autoconf/manual/html_node/Portable-Shell.html.

> karl



-- 
Olaf Weber

               (This space left blank for technical reasons.)