On Nov 24, 2009, at 8:23 PM, Martin Costabel wrote:
> Ben Abbott wrote:
> []
>> Is it possible that the wrong dylib is being loaded at run time? Is there a
>> way to (safely) test the idea?
>
> The other libstdc++ is loaded because it is pulled in by some of the dylibs
> liboctinterp-3.3.50+.d
Ben Abbott wrote:
[]
> Is it possible that the wrong dylib is being loaded at run time? Is there a
> way to (safely) test the idea?
The other libstdc++ is loaded because it is pulled in by some of the
dylibs liboctinterp-3.3.50+.dylib links to, for example
/sw/lib/fltk-aqua/lib/libfltk_gl.1.1.d
On Nov 23, 2009, at 4:39 PM, Martin Costabel wrote:
> Ben Abbott wrote:
>> On Nov 22, 2009, at 10:09 AM, Martin Costabel wrote:
> []
>>> Did the CrashReporter write something in ~/Library/Logs?
>>>
>> []
>> The file below is from ~/Library/Logs/DiagnosticReports.
>
> I don't really know what's
monipol schrieb:
> (...)
>
> Hello, Moritz. I've committed a new version of libical that should fix
> this problem. Could you please test it and tell us if it works for you?
>
Hi,
it worked! Thanks for the support.
Regards,
Moritz
-
Martin Costabel schrieb:
> Moritz Kaiser wrote:
>> Daniel Macks schrieb:
> []
it seems the update of the gimp2-packages refer to a wrong package
name. My fink lists "gcc42", but no "gcc4.2"
>
> The latest revision no longer has a dependency on gcc-4.2.
>
I did my update, and it now start
Moritz Kaiser wrote:
> Daniel Macks schrieb:
[]
>>> it seems the update of the gimp2-packages refer to a wrong package name.
>>> My fink lists "gcc42", but no "gcc4.2"
The latest revision no longer has a dependency on gcc-4.2.
--
Martin
-
