[tex-live] proto10.map and xdvipdfmx in revision 2381

[Jonathan Kew]

On 3 Nov 2006, at 3:46 am, Peter Münster wrote:

> On 2 Nov 2006, Jonathan Kew wrote:
>
>> Very odd -- as it doesn't occur on other systems.
>>
>> Could you send me the Work/tlbuild.log file that results, to see if
>> that gives any clues as to what is failing?
>
> Hello Jonathan,
> I send you attached the tlbuild.log and the texk/xdvipdfmx/config.log

Thanks. I'm not sure what's really causing the problem, but here are  
some things I notice...

(Copying to tex-live list again, as the problem appears to originate  
outside the parts that I have any knowledge about. Seems to be ttf2pk- 
related; see below.)

(1) You are running a prerelease version of gcc (config.log shows  
that it is "gcc version 4.1.2 20060531 (prerelease) (SUSE Linux)"). I  
don't know if this is a factor; most likely it is fine, but if you  
are able to try a different (possibly more stable) version, that  
might be a good experiment.

(2) The xdvipdfmx configure process fails because it tries to use "  
" (space) as the command to run the C preprocessor (CPP). You can see  
this in the config.log file, for example:

========================

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /tmp/texlive-2381/Build/source/texk/xdvipdfmx/ 
missing --run aclocal-1.9'
AMDEPBACKSLASH='\'
AMDEP_FALSE='#'
AMDEP_TRUE=''
AMTAR='${SHELL} /tmp/texlive-2381/Build/source/texk/xdvipdfmx/missing  
--run tar'
AUTOCONF='${SHELL} /tmp/texlive-2381/Build/source/texk/xdvipdfmx/ 
missing --run autoconf'
AUTOHEADER='${SHELL} /tmp/texlive-2381/Build/source/texk/xdvipdfmx/ 
missing --run autoheader'
AUTOMAKE='${SHELL} /tmp/texlive-2381/Build/source/texk/xdvipdfmx/ 
missing --run automake-1.9'
AWK='gawk'
CC='gcc'
CCDEPMODE='depmode=gcc3'
CFLAGS='-g -O2'
CPP=' '
CPPFLAGS=' -I$(top_builddir)/../../texk -I$(top_srcdir)/../../texk'

========================

(3) This bad setting for CPP appears to be coming from the ttf2pk  
configure process; this is shown by grepping your tlbuild.log file  
for "preprocessor\|configuring in":

========================

24:checking how to run the C preprocessor... gcc -E
41:configuring in libs
56:checking how to run the C preprocessor... (cached) gcc -E
72:configuring in t1lib
81:checking how to run the C preprocessor... (cached) gcc -E
120:configuring in type1
129:checking how to run the C preprocessor... (cached) gcc -E
142:configuring in ncurses
159:checking how to run the C preprocessor... (cached) gcc -E
357:configuring in xpdf
390:configuring in freetype
436:checking how to run the C preprocessor... (cached) gcc -E
477:configuring in freetype2
530:checking how to run the C preprocessor... (cached) gcc -E
578:checking how to run the C++ preprocessor... g++ -E
646:configuring in gd
658:checking how to run the C preprocessor... (cached) gcc -E
675:configuring in icu-xetex
712:checking how to run the C preprocessor... (cached) gcc -E
805:configuring in teckit
839:checking how to run the C preprocessor... (cached) gcc -E
851:checking how to run the C++ preprocessor... (cached) g++ -E
927:configuring in utils/dialog
935:checking how to run the C preprocessor... (cached) gcc -E
945:configuring in utils/lcdf-typetools
964:checking how to run the C preprocessor... (cached) gcc -E
969:checking how to run the C++ preprocessor... (cached) g++ -E
1026:configuring in utils/pdfopen
1043:checking how to run the C preprocessor... (cached) gcc -E
1053:configuring in utils/psutils
1061:checking how to run the C preprocessor... (cached) gcc -E
1070:configuring in utils/sam2p
1109:checking how to run the C++ preprocessor... (cached) g++ -E
1160:configuring in utils/t1utils
1179:checking how to run the C preprocessor... (cached) gcc -E
1206:configuring in utils/texi2html
1227:configuring in utils/texinfo
1245:checking how to run the C preprocessor... (cached) gcc -E
1440:configuring in texk
1460:checking how to run the C preprocessor... (cached) gcc -E
1493:configuring in kpathsea
1506:checking how to run the C preprocessor... (cached) gcc -E
1580:configuring in web2c
1595:checking how to run the C preprocessor... (cached) gcc -E
1658:configuring in afm2pl
1678:configuring in bibtex8
1697:configuring in cjkutils
1709:checking how to run the C preprocessor... (cached) gcc -E
1731:configuring in detex
1744:checking how to run the C preprocessor... (cached) gcc -E
1757:configuring in devnag
1775:checking how to run the C preprocessor... (cached) gcc -E
1785:configuring in dtl
1798:checking how to run the C preprocessor... (cached) gcc -E
1874:configuring in dvi2tty
1892:configuring in dvidvi
1905:checking how to run the C preprocessor... (cached) gcc -E
1981:configuring in dviljk
1997:checking how to run the C preprocessor... (cached) gcc -E
2003:configuring in dvipdfm
2011:checking how to run the C preprocessor... (cached) gcc -E
2035:configuring in dvipdfmx
2056:checking how to run the C preprocessor... (cached) gcc -E
2101:configuring in dvipsk
2123:configuring in gsftopk
2141:checking how to run the C preprocessor... (cached) gcc -E
2155:configuring in lacheck
2168:checking how to run the C preprocessor... (cached) gcc -E
2250:configuring in makeindexk
2266:checking how to run the C preprocessor... (cached) gcc -E
2277:configuring in musixflx
2290:checking how to run the C preprocessor... (cached) gcc -E
2366:configuring in ps2pkm
2383:checking how to run the C preprocessor... (cached) gcc -E
2391:configuring in seetexk
2404:checking how to run the C preprocessor... (cached) gcc -E
2481:configuring in tetex
2499:configuring in tex4htk
2512:checking how to run the C preprocessor... (cached) gcc -E
2587:configuring in texlive
2601:checking how to run the C preprocessor... (cached) gcc -E
2675:configuring in ttf2pk
2692:checking how to run the C preprocessor...
2699:configuring in xdv2pdf
2703:configuring in xdvik
2720:checking how to run the C preprocessor... (cached)
2730:checking for preprocessor stringizing operator... yes
2805:configuring in xdvipdfmx
2826:checking how to run the C preprocessor... (cached)
2827:configure:error:C preprocessor " " fails sanity check

========================

Notice how the CPP value was originally "gcc -E", from the top-level  
configure script. This was cached and used by all the sub-configures  
up until ttf2pk. But ttf2pk's configure apparently didn't use the  
cached value, but came up with its own value (blank). This then went  
into the cache, and breaks the subsequent configure of xdvipdfmx. (It  
could also have broken xdvik, but apparently that script didn't  
actually try to use the value.)

So the question becomes why ttf2pk's configure is not behaving  
correctly, and this is not clear to me at the moment. Are you using  
the configure scripts directly as checked-out from TL, or do you run  
reautoconf locally to regenerate them on your system? Do you have  
environment variables that would affect the choice of compiler tools?

One thing that concerns me is that texk/ttf2pk contains both  
configure.in and configure.ac. Presumably one of these is obsolete;  
could it be that the wrong one is being used in generating the  
configure script?

You could try passing --without-ttf2pk to the Build script, to see if  
this will bypass the bad configuration step and then see if xdvipdfmx  
can be configured and built successfully; but of course that would  
not be a real solution, only a workaround for testing purposes.

JK