Need to use the right dlltool for the respective arch
Need to use the right dlltool for the respective arch

Apparently, `-m` still includes some 64 bit objects when running
dlltool. It leads to a linking error when compiling on 32-bit windows:

```
helix-runtime-0-6-3.i386.lib(dnekh.o) : fatal error LNK1112: module
machine type 'x64' conflicts with target machine type 'X86'
```

When analyzing the 32-bit lib file, you can see the 64-bit objects.

```
$ objdump -f helix-runtime-0-6-2.i386.lib
In archive helix-runtime-0-6-2.i386.lib:

dfrzt.o:     file format pe-x86-64
architecture: i386:x86-64, flags 0x00000038:
HAS_DEBUG, HAS_SYMS, HAS_LOCALS
start address 0x0000000000000000

dfrzh.o:     file format pe-x86-64
architecture: i386:x86-64, flags 0x00000039:
HAS_RELOC, HAS_DEBUG, HAS_SYMS, HAS_LOCALS
start address 0x0000000000000000

dfrzs00056.o:     file format pe-i386
architecture: i386, flags 0x00000039:
HAS_RELOC, HAS_DEBUG, HAS_SYMS, HAS_LOCALS
start address 0x00000000
```

This fix ensures we only run the 32-bit dlltool when building the 32-bit
native lib file

tildeio/helix,tildeio/turboruby,tildeio/turboruby,tildeio/helix,tildeio/turboruby,tildeio/helix,tildeio/helix,tildeio/turboruby