RE: Compiling/running code that used to work okay!

2002-05-03 Thread Larry Hall (RFK Partners, Inc)
At 11:07 AM 5/3/2002, Rick Hellicar (QMP) wrote: >Larry Hall wrote: > > At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote: > >> Hi all, > >> > >> I'm modifying some old code I last compiled in October 2000. The code uses a >3rd-party DLL, which > >> comes with an import library. It used to link wit

RE: Compiling/running code that used to work okay!

2002-05-03 Thread Rick Hellicar (QMP)
Larry Hall wrote: > At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote: >> Hi all, >> >> I'm modifying some old code I last compiled in October 2000. The code uses a >3rd-party DLL, which >> comes with an import library. It used to link without fuss against that import >library and run perfectly. >

Re: Compiling/running code that used to work okay!

2002-05-02 Thread Larry Hall (RFK Partners, Inc)
At 10:14 AM 5/2/2002, Rick Hellicar (QMP) wrote: >Hi all, > >I'm modifying some old code I last compiled in October 2000. The code uses a >3rd-party DLL, which >comes with an import library. It used to link without fuss against that import >library and run perfectly. > >I've moved on to cygwin_1

Compiling/running code that used to work okay!

2002-05-02 Thread Rick Hellicar (QMP)
Hi all, I'm modifying some old code I last compiled in October 2000. The code uses a 3rd-party DLL, which comes with an import library. It used to link without fuss against that import library and run perfectly. I've moved on to cygwin_1.3.10, gcc version 2.95.3-5, and I now get a host of "un