Bill, 
Consider distributing windows_build.txt ready to use with 64-bit machines 
and giving the changes to be made for 32-bit machines in comments.  That 
reverses the current orientation, and fits more of the likely user base.  I 
think that change gives you this:


Note that windows_build.txt is preset for 32-bit Windows;
for 64-bit machines, windows_build.txt should be this:

# This is set for use with 64-bit Windows installations
#
#   To use this with  32-bit Windows installations,
#       replace x86_64 with i686 throughout
#       replace ABI=64 with ABI=32


wget http://mpir.org/mpir-2.7.2.tar.bz2
tar -xvf mpir-2.7.2.tar.bz2
cd mpir-2.7.2
./configure --enable-shared --disable-static --enable-gmpcompat 
--build=core2-w64-mingw64 LDFLAGS=-static-libgcc ABI=64
make -j
cd ..
wget http://www.mpfr.org/mpfr-current/mpfr-3.1.4.tar.bz2
tar -xvf mpfr-3.1.4.tar.bz2
cd mpfr-3.1.4
./configure --with-gmp-build=/home/User/mpir-2.7.2 --enable-shared 
--disable-static
make -j
cd ..
git clone https://github.com/wbhart/flint2
https://github.com/wbhart/antic
cd flint2
./configure --enable-shared --disable-static 
--with-mpir=/home/user/mpir-2.7.2 --with-mpfr=/home/user/mpfr-3.1.4 
--extensions=/home/user/antic
# edit Makefile
# in CLFAGS replace -ansi -pedantic with -std=c99
# add -mtune=core2 -march=core2 to CFLAGS
# add -I/home/User/flint2 to INCS
# ensure EXTRA_SHARED_FLAGS contains -static-libgcc -shared 
-Wl,--export-all-symbols
make -j
cd ..
wget http://pari.math.u-bordeaux.fr/pub/pari/unix/pari-2.7.6.tar.gz
tar -xvf pari-2.7.6.tar.gz
cd pari-2.7.6
export PATH=/home/user/mpir-2.7.2/.libs:$PATH
LDFLAGS=-static-libgcc CFLAGS="-mtune=core2 -march=core2" ./Configure 
--with-gmp-include=/home/user/mpir-2.7.2 
--with-gmp-lib=/home/user/mpir-2.7.2/.libs --host=x86_64-pc-mingw
cd Omingw-x86_64-pc
make gp
cd ../..




On Friday, October 28, 2016 at 4:54:06 AM UTC-4, Bill Hart wrote:
>
> 64 bit Windows will run 32 bit Windows binaries, yes. Of course we 
> recommend the 64 bit ones.
>
> On 28 October 2016 at 10:52, digxx <diger...@hotmail.com <javascript:>> 
> wrote:
>
>> Yes but when I do not manually change i686 and ABI=32 to the x64 it is 
>>> running the 32bit version, right?
>>> You mean windows 64 can still cope with 32bit stuff? 
>>>
>>
>>
>> I mean changing in the windows_build.txt
>> By Pkg.build("Nemo") I do not run any executable, right? 
>>
>
>

Reply via email to