for the record - with the 32 bit libraries and "__cdec" defined for al functions, all works fine. ----- Original Message ----- From: Ray Holme <rayholme@xxxxxxxxx> To: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>; "gcc-help@xxxxxxxxxxx" <gcc-help@xxxxxxxxxxx> Cc: Sent: Thursday, May 3, 2012 2:43 PM Subject: Re: trying to build a DLL on Windows 7 gcc using 3rd party libraries Got it and thanks. Downloading the 32 bit version when the server comes back up. Will notify all of the results. Hoping for sucess. ----- Original Message ----- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx> To: gcc-help@xxxxxxxxxxx Cc: Sent: Thursday, May 3, 2012 2:33 PM Subject: Re: trying to build a DLL on Windows 7 gcc using 3rd party libraries 3.5.2012 19:35, Ray Holme kirjoitti: > I may have found the problem here, but I am in Microsoft land and am not sure of myself. > It would appear that the version of gcc that I installed is 32 bit - the name is MINGW32. > It would appear that the version of the firebird software is 64 bit so the libraries are 64 bit. If the "firebird" means the following : http://www.firebirdsql.org/en/firebird-2-5-1/ then there shouldn't be any mistake about what one has downloaded and what not... I downloaded both the 32-bit and 64-bit ZIP-packages and looked if my 'i586-mingw32' target binutils could handle these files. The result was : - the 32-bit 'fbclient_ms.lib' could be viewed nicely with 'nm', 'objdump' etc. - the 64-bit 'fbclient_ms.lib' could not be viewed with 'nm', 'objdump' etc. Seemingly my GNU binutils for MinGW host/target were too old : C:\opt\firebird64\lib>\opt\cross\i586-mingw32\bin\objdump --version GNU objdump (Linux/GNU Binutils) 2.17.50.0.16.20070511 Generally I'm not aware of the 64-bit MinGW situation, using the 32-bit 'Firebird-2.5.1.26351-0_Win32.zip' or some earlier version could work with the 32-bit MinGW tools, I think...
