| Newsgroups |
gmane.mail.blat |
| Message-ID |
<[email protected]> |
>From: [email protected] mailto:[email protected] [mailto:[email protected] mailto:[email protected]]
>There is a discussion at Source Forge
>(https://sourceforge.net/p/blat/bugs/64/ https://sourceforge.net/p/blat/bugs/64/)
>where a fellow identified an issue with Blat that he believes is a bug
>in the code itself. I checked the issue, and found that the problem is
>not in Blat source, but is rather in the Microsoft Visual Studio
>compiler library code against which Blat is built. Furthermore, the
>issue does not exist with the 64-bit version of Blat.
>The issue is basically this, when the full path to Blat is used on the
>command line, or within a script, and that path uses quotation marks
>for only the path itself, the command line is not parsed in 32-bit mode
>the same way as it is parsed in 64-bit mode. This difference means
>that Blat is given one additional argument that should not be present,
>this additional value is the name of Blat executable.
>For example:
>"R:\Program Files\NoInstallReqd\Blat"\blat.exe –h
>would result in Blat being give the following before it has a chance to
>do anything:
>argument #1 = R:\Program Files\NoInstallReqd\Blat argument #2 =
>\blat.exe argument #3 = –h
>The middle argument from above is not right, it was supposed to be part
>of the first argument. The net result is that Blat is not able to
>find “\blat.exe” as a message file and will exit with an error.
>I would suggest folks go read the thread on Source Forge, then leave
>comments either at that site and/or post responses here.
It would be interesting to see what happens with the gcc compilers,
both the original MinGW 32-bit compiler and the 64-bit and 32-bit
compilers from the MinGW-64 project. The original MinGW 32-bit
gcc uses a runtime library that has some substantial differences
from the ones used by the MinGW-64 project's compilers, so it
would be a good idea to test with all of them.