<html><body> <DIV>Thank you Brian for working with me on this.  All is good, now!  I'll give you a mention in my thesis paper, and send you a copy when I'm finished!</DIV> <DIV> </DIV> <DIV>Cheers!</DIV> <DIV> -Dave</DIV> <DIV> </DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR><BR>> Paul Leyland wrote: <BR>> > On Thu, 2005-04-14 at 13:12, mrgrynch@comcast.net wrote: <BR>> > <BR>> >>I have some more information in support of a problem with the build <BR>> >>paths. <BR>> >> <BR>> >>I moved the x86i folder to D\_temp, changed to the folder to <BR>> >>D:\_temp\x86i\pentium4\sse2 and executed the following: <BR>> >> <BR>> >>D:\_temp\x86i\pentium4\sse2>nasm -O9 -Xvc -f win32 -o "submul_1.obj" <BR>> >>"submul_1.asm" <BR>> >> <BR>> >>This worked. <BR>> > <BR>> > Good. That's roughly what I suggested, I think --- give an explicit <BR>> > path to nasm. <BR>> <BR>> After a bit of detective work, this problem turned out to be the result <BR>> of an internal NASM feature and not a difficulty in locating the NASM <BR>> executable. <BR>> <BR>> It is a problem that I have reported to the NASM team with a fix but <BR>> they have declined to implement this. <BR>> <BR>> Fortunately there is no problem with YASM so I now intend to move over <BR>> to this assembler in place of NASM for my native GMP port. <BR>> <BR>> Brian Gladman <BR>> <BR>> _______________________________________________ <BR>> gmp-discuss mailing list <BR>> gmp-discuss@swox.com <BR>> https://gmplib.org/mailman/listinfo/gmp-discuss </BLOCKQUOTE></body></html>