<html><body> <DIV>I have some more information in support of a problem with the build paths.</DIV> <DIV> </DIV> <DIV>I moved the x86i folder to D\_temp, changed to the folder to D:\_temp\x86i\pentium4\sse2 and executed the following:</DIV> <DIV> </DIV> <DIV>D:\_temp\x86i\pentium4\sse2>nasm -O9 -Xvc -f win32 -o "submul_1.obj" "submul_1.asm"</DIV> <DIV> </DIV> <DIV>This worked.</DIV> <DIV> </DIV> <DIV>Regards,</DIV> <DIV> -Dave</DIV> <DIV> </DIV> <DIV> </DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR><BR>> mrgrynch@comcast.net wrote: <BR>> > I've been trying to build Brian Gladman's Win32 port of GMP, but cannot <BR>> > seem to get the assembly code to work. I've downloaded the NASM <BR>> > compiler, placed it in it's own folder, and set my path. Typing "nasm" <BR>> > from the command line (any command line) is able to find the program <BR>> > without a problem. <BR>> > <BR>> > Attempting to build ANY of the assembly code portion, however, responds <BR>> > with the output below. Any assistance would be appreciated. <BR>> > <BR>> > Thanks, <BR>> > -Dave <BR>> > <BR>> > ------ Rebuild All started: Project: lib_mpn_p4, Configuration: Debug <BR>> > Win32 ------ <BR>> > <BR>> > Deleting intermediate files and output files for project 'lib_mpn_p4', <BR>> > configuration 'Debug|Win32'. <BR>> > <BR>> > Performing Pre-Build Event... <BR>> > <BR>> > 1 file(s) copied. <BR>> > <BR>> > 1 file(s) copied. <BR>> > <BR>> > 1 file(s) copied. <BR>> > <BR>> > Performing Custom Build Step <BR>> > <BR>> > The system cannot execute the specified program. <BR>> > <BR>> > Project : error PRJ0019: A tool returned an error code from "Performing <BR>> > Custom Build Step" <BR>> <BR>> You need to put the NASM executable in the VC++ binary folder, which is: <BR>> <BR>> C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin <BR>> <BR>> on my system (note that this is different on VC6 and VC8 beta). <BR>> <BR>> You aslo need to make sure that the NASM executable is called nasm.exe <BR>> and not nasmw.exe. <BR>> <BR>> I am happy to help with any other problems you run into. <BR>> <BR>> Brian Gladman <BR>> </BLOCKQUOTE></body></html>