11 Dec 2007 19:28
[ xdvi-Feature Requests-1819017 ] uint32_t conflicts with XeTeX configure
SourceForge.net <noreply <at> sourceforge.net>
2007-12-11 18:28:22 GMT
2007-12-11 18:28:22 GMT
Feature Requests item #1819017, was opened at 2007-10-24 13:59 Message generated for change (Comment added) made by tutimura You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=377583&aid=1819017&group_id=23164 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Feasibility: 1 (easy) Group: Usability Improvement 4 Status: Closed Priority: 5 Private: No Submitted By: Nobuyuki Tsuchimura (tutimura) Assigned to: Stefan Ulrich (stefanulrich) Summary: uint32_t conflicts with XeTeX configure Initial Comment: 'xdvik' uses 'uint32_t', and XeTeX also uses 'uint32_t'. Their definitions are slightly different from each other. This is almost OK, unless they are merged into one configure like TeX Live. In my environment (RedHat base Linux), this cause an error while configuring TeX Live 2007. XeTeX configure alone recognizes we have the system defined 'uint32_t', and 'xdvik' configure along recognizes we don't. So the merged configure gets confused with the cached result. To solve this problem in simple way, we can let 'uint32_t' be the same. We have two ways, one is to fix xdvik, another is to fix XeTeX.(Continue reading)
RSS Feed