<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Angelo Graziosi wrote:<br>
</div>
<blockquote cite="mid:020833e4-1974-1c63-53d4-f36b95ea5b6b@alice.it"
type="cite">Philip Taylor wrote:
<br>
<blockquote type="cite">Delighted to learn from Vincent Torri that
one can, at least in
<br>
theory, build a 64-bit TeX Live for Windows, and having overcome
<br>
a couple of initial hurdles, I can now, like Vicent, perform a :
<br>
<br>
<tt>./Build --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32
</tt><br>
<br>
within the context of an <tt>Msys</tt> command-line window.
<br>
</blockquote>
<br>
Which "<tt>Msys</tt> command-line window"?
<br>
<br>
Please, explain.. <br>
</blockquote>
At first I did not have <tt>Msys</tt> at all, and did not realise
that it was needed. Needless to say, "<tt>./Build</tt>" failed
horribly at a CMD prompt. I then installed "<tt>msys-base</tt>"
from the MinGW GUI installer window (and later, <tt>mingw32-gcc-g++</tt>
and <tt>mingw-developer-toolkit</tt>, when I found that one or both
were needed), created a shortcut called "<tt>Msys</tt>" in <tt>D:\MinGW\msys\1.0</tt>
with "<tt>Start in</tt>" set to <tt>D:\MinGW\msys\1.0\bin</tt> as
recommended in Msys.bat :<br>
<blockquote type="cite"><tt>rem ember to set the "Start in:" field
of the shortcut.</tt><tt><br>
</tt><tt>rem A value similar to C:\msys\1.0\bin is what the "Start
in:" field needs</tt><tt><br>
</tt><tt>rem to represent.</tt></blockquote>
but still encountered problems (such as "<tt>No C compiler in path</tt>").<br>
<br>
Finally I added <tt>D:\MinGW\bin, D:\Mingw\Msys\1.0 </tt>and <tt>D:\Mingw\Msys\1.0\bin</tt>
to the front of the system-wide path, launched a normal CMD window
(in order to pick up the modified path) and typed "<tt>Msys</tt>".
<br>
<br>
That launched the Msys window to which I referred in my earlier
message.<br>
<br>
Whether this will allow me to compile and link XeTeX, I still do not
know; it has been running now for about two hours, and still shews
no signs of completion. The incantation to launch this was taken
and modified from Karl's "Build one package" instructions :<br>
<br>
<blockquote type="cite">
<pre class="example"># Create build directory:
mkdir Work
cd Work
</pre>
</blockquote>
<blockquote type="cite">
<pre class="example">
# Do the configure:
../configure --disable-all-pkgs --enable-xetex -C CFLAGS=-g CXXFLAGS=-g
# Do the make:
make</pre>
</blockquote>
but I am not yet in a position to try :
<blockquote type="cite">
<pre class="example"># Test:
cd texk/dvipdfm-x
make check</pre>
</blockquote>
Of course, this is a 32-bit build; only once that works will I try
to see if I can work out how to convert :<br>
<br>
<blockquote type="cite"><tt>./Build --build=x86_64-w64-mingw32
--host=x86_64-w64-mingw32
</tt></blockquote>
into the corresponding incantations for "Configure" and/or "Make".<br>
<br>
<div class="moz-signature">-- <br>
<img src="cid:part1.E0A5C2BC.BCC0A32E@Rhul.Ac.Uk"><br>
Philip Taylor</div>
<br>
<br>
</body>
</html>