-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, (it's one of those sleepless nights here, firecrackers & what-not ;) ) > [...] > set -x; LD_LIBRARY_PATH=../../../exports/lib FONTCONFIG_PATH=../../../lib/fontconfig ../../../exports/bin/fc- cache -f -v /home/kevinzhu/X11R6/lib/X11/fonts/misc > + LD_LIBRARY_PATH=../../../exports/lib > + FONTCONFIG_PATH=../../../lib/fontconfig > + ../../../exports/bin/fc-cache -f -v /home/kevinzhu/X11R6/lib/X11/fonts/misc > /bin/sh: ../../../exports/bin/fc-cache: cannot execute binary file > make[4]: *** [install] Error 126 > make[4]: Leaving directory `/home/kevinzhu/TinyXR46/build/fonts/bdf/misc' > make[3]: *** [install] Error 2 > make[3]: Leaving directory `/home/kevinzhu/TinyXR46/build/fonts/bdf' > make[2]: *** [install] Error 2 > make[2]: Leaving directory `/home/kevinzhu/TinyXR46/build/fonts' > make[1]: *** [install] Error 2 > make[1]: Leaving directory `/home/kevinzhu/TinyXR46/build' > make: *** [install] Error 2 I can only guess -- fc-cache is made to run during the install phase of fontconfig. Check to be sure your $DISPLAY env-var is set to a valid number such as: export DISPLAY=:0.0 or similar, depending on the shell you're using. IIUC the fc-cache pgm usually does not need X11 to be actually running, it just needs a fake but valid $DISPLAY setting. I've seen it happen even when building the full X11 on 'official' platforms. ;) -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 2.5 wkYEARECAAYFAkaLQkIACgkQZbt5KOxKrtQz/wCeJfp2h4XxBKsH1DWYGOMe5YyV974A n20pMRcTdQAD4x+ecnBQrY1pwZIN =95fk -----END PGP SIGNATURE----- _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
