[XeTeX] Building TECkit

Peter Dyballa Peter_Dyballa at Web.DE
Mon Dec 27 21:56:20 CET 2010


Am 27.12.2010 um 20:30 schrieb Dominik Wujastyk:

> Any suggestions?  I've made TECkit successfully in the past (a year  
> ago?).


Sprintf is a basic function. Maybe its declaration is guarded by  
something in its header file. To find out which header files are used  
you can modify the compilation by inserting "-H" (without the quotes)  
for example before "-g". Then the compiler would output a large list  
of lines starting with one or more "." followed by a SPACE and then  
the pathname of such a header file. Then grep for sprintf in these  
files (you should have success with stdio.h, probably in /usr/ 
include). Now check whether the definition is in some #ifdef or  
#ifndef! Is it necessary #define (or #undef) something that the  
definition os sprintf is reached?

You might also try to substitute the "-c" in the compilation command  
with "-E -dD" and "-o .libs/Compiler.o" with "-o  
Compiler.preprocessed" and search in this output file the place where  
the definition of sprintf should have happened (you'll comments about  
inclusion of a header file and which line in which file had caused  
it). Now compare the code on the preprocessed output file with that in  
the original header file. Which #defs had caused the caused? Which one  
is missing, has prevented the definition of sprintf?


Can you compile with the compiler(s) you used last christmas? With a  
package management system it should be an easy task to swap them.

--
Greetings

   Pete

Almost anything is easier to get into than out of.
				– Allen's Law




More information about the XeTeX mailing list