On 15/09/2014 06:05, simpsonj...@gmail.com wrote: > Hello to all and thanks for making a VS version of MPIR! > > My name is John. This is my first experience with MPIR. I have attempted to > build MPIR 2.7.0 alpha11 today as follows ... > > (1) Downloaded zip file version onto Dell XPS 8700 > (1.1) Windows 7 Professional Service Pack 1 > (1.2) Intel Core i7-4790 @ 3.6GHz > (1.3) 16GB Memory > (1.4) 2TB Hard disc > (2) Downloaded using Google Chrome Version 37.0.2062.120 m > (3) Unzipped using 7-Zip 9.20 into working directory under download directory > (4) Selected all files in working directory and click-drag-copied into c:\mpir > (5) Downloaded Python 3.4.1 and installed as c:\Python3.4 > (6) Downloaded vsyasm-1.3.0-win64 and copied into C:\Program Files > (x86)\Microsoft Visual Studio 12.0\VC\bin > (7) initiated build process by following MPIR Edition 2.7.0 5 April 2014 > Doucment > (7.1) page 12 2.4.0 Building with Micro Visual Studio ... Building MPIR > (7.2) A build of MPIR is started by double clicking on the file 'mpir.sln' in > the appropriate sub-directory: Visual Studio 2013: mpir/build.vc12/mpir.sln > (7.3) Visual Studio will then display a list of individual build projects > (7.3.1) Visual Studio Express 2013 for Windows Desktop Version 12.0.21005.1 > REL appears when C:\mpir\build.vc12\mpir.sln is double clicked > (7.3.2) Solution 'mpir' (13 projects) is created in Solution Explorer > (7.3.3) dll_mpir_core2 through lib_mpir_sandbridge appear as available > projects > (8) page 12 2.4.0 Building MPIR ... "Before a project is built, Visual Studio > should be set to the required configuration (Release or Debug) and then > required target architecture (win32 or x64). The build process put the output > files into one of the sub-directories: 'mpir/lib' or 'mpir/dll' depending on > whether static library or DLL versions have been built. > (8.1) VS Express 2013 defaults to Debug and Win32 the first time it is invoked > (8.2) right clicking on the dll_mpir_core2 project icon in Solution Explorer > and then clicking on Project Only>Build Only>dll_mpir_core2 generates the > following error > (8.3) Error 1 error MSB3721: The command ""C:\Program Files (x86)\Microsoft > Visual Studio 12.0\VC\bin\"vsyasm.exe -Xvc -f x64 -g cv8 -i > "..\..\mpn\x86_64w\\" -d "DLL" -o "x64\Debug\mpn\\" -rnasm -pnasm > ..\..\mpn\x86_64w\add_err1_n.asm ..\..\mpn\x86_64w\add_err2_n.asm > ..\..\mpn\x86_64w\core2\add_n.asm ..\..\mpn\x86_64w\core2\addadd_n.asm > ..\..\mpn\x86_64w\core2\addlsh1_n.asm ..\..\mpn\x86_64w\core2\addlsh_n.asm > ..\..\mpn\x86_64w\core2\addmul_1.asm ..\..\mpn\x86_64w\core2\addmul_2.asm > ..\..\mpn\x86_64w\core2\addsub_n.asm ..\..\mpn\x86_64w\core2\and_n.asm > ..\..\mpn\x86_64w\core2\andn_n.asm ..\..\mpn\x86_64w\core2\com_n.asm > ..\..\mpn\x86_64w\core2\copyd.asm ..\..\mpn\x86_64w\core2\copyi.asm > ..\..\mpn\x86_64w\divexact_1.asm ..\..\mpn\x86_64w\divexact_by3c.asm > ..\..\mpn\x86_64w\core2\divexact_byff.asm > ..\..\mpn\x86_64w\divexact_byfobm1.asm ..\..\mpn\x86_64w\divrem_2.asm > ..\..\mpn\x86_64w\divrem_euclidean_qr_1.asm > ..\..\mpn\x86_64w\divrem_euclidean_qr_2.asm ..\..\m pn\x86_64w\core2\divrem_hensel_qr_1_2.asm ..\..\mpn\x86_64w\core2\hamdist.asm ..\..\mpn\x86_64w\core2\ior_n.asm ..\..\mpn\x86_64w\core2\iorn_n.asm ..\..\mpn\x86_64w\core2\karaadd.asm ..\..\mpn\x86_64w\core2\karasub.asm ..\..\mpn\x86_64w\core2\lshift.asm ..\..\mpn\x86_64w\core2\lshift1.asm ..\..\mpn\x86_64w\core2\mod_1_1.asm ..\..\mpn\x86_64w\core2\mod_1_2.asm ..\..\mpn\x86_64w\core2\mod_1_3.asm ..\..\mpn\x86_64w\modexact_1c_odd.asm ..\..\mpn\x86_64w\core2\mul_1.asm ..\..\mpn\x86_64w\core2\mul_2.asm ..\..\mpn\x86_64w\core2\mul_basecase.asm ..\..\mpn\x86_64w\mulmid_basecase.asm ..\..\mpn\x86_64w\core2\nand_n.asm ..\..\mpn\x86_64w\core2\nior_n.asm ..\..\mpn\x86_64w\core2\popcount.asm ..\..\mpn\x86_64w\core2\redc_1.asm ..\..\mpn\x86_64w\core2\rsh1add_n.asm ..\..\mpn\x86_64w\core2\rsh1sub_n.asm ..\..\mpn\x86_64w\core2\rsh_divrem_hensel_qr_1_2.asm ..\..\mpn\x86_64w\core2\rshift.asm ..\..\mpn\x86_64w\core2\rshift1.asm ..\..\mpn\x86_64w\sqr_basecase.asm ..\..\mpn\x8 6_64w\core2\store.asm ..\..\mpn\x86_64w\sub_err1_n.asm ..\..\mpn\x86_64w\sub_err2_n.asm ..\..\mpn\x86_64w\core2\sub_n.asm ..\..\mpn\x86_64w\core2\subadd_n.asm ..\..\mpn\x86_64w\core2\sublsh1_n.asm ..\..\mpn\x86_64w\core2\submul_1.asm ..\..\mpn\x86_64w\core2\sumdiff_n.asm ..\..\mpn\x86_64w\core2\udiv_qrnnd.asm ..\..\mpn\x86_64w\core2\umul_ppmm.asm ..\..\mpn\x86_64w\core2\xnor_n.asm ..\..\mpn\x86_64w\core2\xor_n.asm" exited with code 1. C:\mpir\build.vc12\vsyasm.targets 45 5 dll_mpir_core2
Hi John, Thank you for the comprehensive report on your experience with building MPIR with Visual Studio. For reasons I don't yet understand, it seems that the assembler build step (8.3) has failed. To check out possible reasons can you check if a single file builds by navigating in the solution explorer to: mpir_dll_core2/Source Files/mpn/yasm/add_err1_n.asm right clicking on this file and selecting Compile. This should assemble this single file and hence checks if the vsyasm assembler is working properly. > (8.4) Reference (8) above: no mpir/lib mpir/dll are NOT present at this point > (8.5) C:\mpir\build.vc12\dll_mpir_core2: now has an x64 directory > (8.6) C:\mpir\build.vc12\dll_mpir_core2\x64: has a debug directory > (8.7) C:\mpir\build.vc12\dll_mpir_core2\x64\Debug: contains the following > (8.7.1) dll_mpir_core2.tlog directory which contains > (8.7.1.1) dll_mpir_core2_lastbuildstate containing 150 bytes as follows > (8.7.1.1.1)#TargetFrameworkVersion=v4.0:PlatformToolSet=v120:EnableManagedIncrementalBuild=false:VCToolArchitecture=Native32Bit > Debug|x64|C:\mpir\build.vc12\| > (8.7.1.2) unsuccessfulbuild which is empty > (8.7.2) mpn directory which is empty > (8.7.3) dll_mpir_core2.txt > (8.7.4) dll_mpir_core2.write.1.tlog > (9) This is as far as I got today > (9.1) I discovered there is a prebuild and postbuild patch file but didn't > run these prior to performing the build process described above. I am not aware of any patch files in the build. There are pre and post build batch files but these are automatically used during the build process so manual intervention is not needed. You are almost there - if we can find out why the assembler step is failing, we should be able to get your build working. Brian -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
