Re: GLIB and MinGW

Earnie wrote:
> Dieter Verfaillie wrote:
>> On Sat, 8 Oct 2011 13:26:23 -0400, Earnie Boyd wrote:
>>> I've built version 2.29.92 with MinGW's gcc version 4.6.1 and
>>> binutils version I'm seeing a SIGSEGV error
>>> caused from an infinite loop at line 732 of glib/gatomic.c (as
>>> seen by the bt from gdb). The calling program dbus-glib-tool
>>> calls g_type_init () and never returns. The relative bt is below.
>>> I'm trying to build Xiphos which still has a requirement for
>>> dbus-glib-1. I'm currently doing a rebuild with CFLAGS set with
>>> -O0 instead of -O2 to see if it helps but are there other
>>> suggestions?
>> I've been forcing usage of gcc atomic ops ever since
>> instead of
>> relying on the fallback implementation.
>> So I still have the patch from that bug report marked "rejected"
>> applied here. By doing so you're also forced to ./configure with
>> -march=i486 or higher.
> Thanks for the quick reply. I'll definitely give it a try. Who's
> still using i386 anyway?? Or i486 for that matter. ;)

With Dieter's response I was able to modify my config.status file to get
past this issue.  There are already issues open in the tracker items for
MinGW to add atomic support as well as MemoryBarrier.  MemoryBarrier
however is only supported for Windows 2000 which I see at that is the minimum requirement
for the prebuilt distributions.  But MemoryBarrier doesn't need to be
used for XP since it isn't supported.  Hopefully any use of
MemoryBarrier is controlled by proper #if WINVER >= 0x0502 declarations.

Now on to other required GTK libraries.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]