Re: [Openocd-development] [Tiff] Potential problem in libtiff when compiled in MinGW

2009-05-17 Thread Øyvind Harboe
>> Since MinGW uses older msvcrt.dll which is unlikely to be updated >> (API-wise), that situation will probably remain. > > Switching to a more conformant printf utility sounds good then. > The Linux one is nice.  ;) I just hate the idea of trying to map out all the quirks of an older printf() th

Re: [Openocd-development] [Tiff] Potential problem in libtiff when compiled in MinGW

2009-05-17 Thread David Brownell
On Sunday 17 May 2009, Igor Skochinsky wrote: > None of the MSVC runtime libraries support %ll, you have to use %I64. Let's hear it for Microsoft's conformance to standard!!! (sound of crickets chirping...) > Since MinGW uses older msvcrt.dll which is unlikely to be updated > (API-wise), tha

Re: [Openocd-development] [Tiff] Potential problem in libtiff when compiled in MinGW

2009-05-17 Thread Igor Skochinsky
Hello Bob, Sunday, May 17, 2009, 6:44:41 PM, you wrote: BF> I see. MinGW depends on whatever library happens to be installed so BF> %ll may work on some Windows systems (which happen to have an BF> updated library) and not on others. None of the MSVC runtime libraries support %ll, you have to u