On May 5, 2008, at 10:02 PM, Martin Costabel wrote:
> Alexander Hansen wrote:
> []
>> I've pulled a bit of the build log that I got.
>> Making all in auto
>> if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H
>> -I. -I. -I../.. -I../../include
>> -DDEBUG_NAMESPACE='"libggi.displ
Alexander Hansen wrote:
[]
> I've pulled a bit of the build log that I got.
>
> Making all in auto
> if /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H
> -I. -I. -I../.. -I../../include
> -DDEBUG_NAMESPACE='"libggi.display.auto"' -I/sw/include -I/sw/include
> -g -O2 -I/sw/include
-- Forwarded message --
From: Pepe Barbe <[EMAIL PROTECTED]>
Date: Sat, May 3, 2008 at 12:02 AM
Subject: Re: [Fink-devel] build failure in lbggi2-2.0.1-1012
To: Alexander Hansen <[EMAIL PROTECTED]>
I am having a similar problem on 10.5.2/Intel.
Attached is the output of the buil
Warnings are relatively harmless (those are really just memory, leaks,
no memory corruptions). Usually, such warnings happen when you create
the new thread, use objective-c memory-allocations on it, but do not
create Autorelease Pool for that thread
and segfault should be rtaced with gdb, I guess.
