Re: Reducing Linker Bugs

2011-12-19 Thread dsimcha
On 12/19/2011 12:54 AM, Walter Bright wrote: On 12/18/2011 8:38 PM, dsimcha wrote: Two questions: 1. What's the best way to file a bug report against Optlink when I get one of those Optlink terminated unexpectedly windows and I'm linking in libraries that I don't have the source code to and

Re: Reducing Linker Bugs

2011-12-19 Thread Walter Bright
On 12/19/2011 5:51 AM, dsimcha wrote: On 12/19/2011 12:54 AM, Walter Bright wrote: On 12/18/2011 8:38 PM, dsimcha wrote: Two questions: 1. What's the best way to file a bug report against Optlink when I get one of those Optlink terminated unexpectedly windows and I'm linking in libraries that

Re: Reducing Linker Bugs

2011-12-19 Thread dsimcha
The OMF library that I don't have the source to is a BLAS/LAPACK stub library that calls into a DLL. It was uploaded ~5 years ago to DSource by Bill Baxter. I know absolutely no details about how he compiled it. On Monday, 19 December 2011 at 18:04:26 UTC, Walter Bright wrote: On

Reducing Linker Bugs

2011-12-18 Thread dsimcha
Two questions: 1. What's the best way to file a bug report against Optlink when I get one of those Optlink terminated unexpectedly windows and I'm linking in libraries that I don't have the source code to and thus can't reduce? 2. I'm getting on the Optlink hating bandwagon. How hard

Re: Reducing Linker Bugs

2011-12-18 Thread Andrej Mitrovic
I've tried #2 before but it only worked for the most trivial code. As a workaround you could try unilink (OMF-compatible): ftp://ftp.styx.cabel.net/pub/UniLink/ulnb0329.zip Change ulink.cfg to e.g.: -zsnn.lib -LC:\dmd\windows\lib -LC:\dm\lib -Go

Re: Reducing Linker Bugs

2011-12-18 Thread Walter Bright
On 12/18/2011 8:38 PM, dsimcha wrote: Two questions: 1. What's the best way to file a bug report against Optlink when I get one of those Optlink terminated unexpectedly windows and I'm linking in libraries that I don't have the source code to and thus can't reduce? In that case, the best