Seemingly patternless optlink premature termination

[pineapple via Digitalmars-d]

On Monday, 9 January 2017 at 02:34:31 UTC, Jerry wrote:
> before I switched away from optlink. What point is there to 
> report these bugs though, Microsoft's linker works with fewer 
> bugs and actually supports the format of the platform. So no 
> need to convert .lib files with it. This is my point, it's just 
> one more thing that has to be maintained, but it's not even 
> being maintained. Supporting MinGW would be a better option as 
> then you don't have to maintain the linker and not have it 
> degrade over time.

On this subject, I spent a good chunk of my day trying to compile 
my code using the -m32mscoff switch and was never able to get it 
to work. (My most recent obstacle is this error, occurring even 
for a very simple test program importing no dependencies, if 
anyone cares to take a look: https://hastebin.com/vezojehaxo.txt)

On Monday, 9 January 2017 at 01:27:27 UTC, Walter Bright wrote:
> On 1/8/2017 12:58 PM, pineapple wrote:
>> On Sunday, 8 January 2017 at 18:49:50 UTC, Walter Bright wrote:
>>> Please post bug reports to bugzilla.
>>
>> Here you go: https://issues.dlang.org/show_bug.cgi?id=17077
>
> Thank you.

Regarding the above: Because I have not managed to get an 
alternative to optlink working, I currently am unable to work on 
mach on my Windows desktop. In order to keep up progress I've 
been having to write and compile code on OSX on a laptop; it is 
nowhere near an ideal workflow. I understand you likely have a 
lot on your plate, but please prioritize solving this problem. 
It's causing me a great deal of irritation and inconvenience, and 
it's embarrassing that my library now simply won't compile on 
Windows.