Hello, FYI, I asked wx developers about the issue:
------ Forwarded message ------ From: Vadim Zeitlin <[email protected]> Date: Mon, 14 Dec 2009 14:13:43 +0100 Subject: Re: [wx-dev] Fw: Re: cross building wxMSW under fedora 12 configure error: cannot compute sizeof (boolean), 77) To: [email protected] On Mon, 14 Dec 2009 14:19:21 +0200 Nerijus Baliunas <[email protected]> wrote: NB> what does wx do with libjpeg boolean now? When building libjpeg ourselves we rename boolean to wxjpeg_boolean (which is still int, as original boolean). I had several problems because of this though so I almost convinced myself that it would be better to just let Windows define boolean as "unsigned char" and use this definition -- libjpeg seems to still work just fine with it. NB> The w32api header rpcndr.h contains a definition for the boolean data NB> type. However, this definition differs from what libjpeg thinks a NB> boolean is. This resulted in compile errors and strange segfaults: NB> https://bugzilla.redhat.com/show_bug.cgi?id=497492 NB> NB> To fix these compile errors and strange segfaults we decided to rename NB> libjpeg's boolean definition to 'jpeg_boolean'. Every program/library NB> which uses libjpeg should be patched to use 'jpeg_boolean' instead of NB> 'boolean' to avoid any confusion. However if Fedora chose to fix it in almost the same way as we did, it's probably simpler/safer to follow their lead and just rename wxjpeg_boolean to jpeg_boolean. OTOH I'm as confused about the upstream libjpeg status as people in the Bugzilla discussion mentioned above are... Does anybody know who IJG is? Regards, VZ -------- End of message ------- _______________________________________________ fedora-mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
