Subject Re: Firebird 1.5 will not build on MinGW; who do I contact.??
Author rdsmith1465
--- In firebird-support@yahoogroups.com, "Dimitry Sibiryakov" <SD@...>
wrote:
>
> On 26 Feb 2006 at 2:39, rdsmith1465 wrote:
>
> >Blas Samoza says he's off the project.
> >
> >Does anyone know what I should do?
>
> You could contact me...
> About MinGW build of FB1.5: it is broken indeed and won't be fixed
> because it is not considered "mainstream".
>
> --
> SY, Dimitry Sibiryakov.
>
Hi Dimitry:

Thanks for the reply. I sent the message below to aafemt@... back
in December, since that was the contact listed on the MINGW Notes.
You say the build is broken, and will not be fixed - why haven't the
MINGW notes either: been removed; or amended?

Thanks,

Randall Smith

========= Previously sent message ===========


Hi Dimitry:

I'm emailing you, since your email is on the README.build.mingw.html.

It breaks for me.

First problem is gpre.h, which attempts to redefine USN, yielding:

In file included from ../src/gpre/cmd.cpp:33:
../src/gpre/gpre.h:1475: conflicting types for `typedef struct
usn*USN'
f:/Programs/MinGW/include/winnt.h:147: previous declaration as
`typedef LONGLONG USN'

Now, the USN in Firebird is not the same sort of typedef as defined in
winnt.h, so I can do some renaming in
gpre.h and get around that.
The next problem is ld doen't search the /mingw/lib path to get
libmpr.a (among others). I can patch the rules file and
add a switch, getting around that.

Put THEN I get hundreds of those nightmare "undefined reference to
_XXXXXXXX" or
"undefined reference to SomeMethod@4" messages.

What's going on? Does MinGW just work differently (correctly) for you?
Who should I address regarding this issue (if not yourself?)

Thanks for your time,

Randall Smith