On Mon, 28 Apr 2008 00:01:45 +
xsdg [EMAIL PROTECTED] wrote:
Did you make sure to `export LD_LIBRARY_PATH`? (I'm not sure what the
equivalent might be for different shells). This is likely the problem
if you see a difference between the output of
Yup. The wrapper script does that, but
On Mon, 28 Apr 2008 00:01:45 +
xsdg [EMAIL PROTECTED] wrote:
Well. I compiled it with --enable-shared=no --enable-static=yes, and it works
fine. It seems slightly faster on some operations (Although I could easily be
imagining that), but sadly still doesn't resolve my issue of the CMYK
On Mon, Apr 28, 2008 at 6:26 PM, Jon Senior wrote:
Well. I compiled it with --enable-shared=no --enable-static=yes,
and it works fine. It seems slightly faster on some operations (Although
I could easily be imagining that), but sadly still doesn't resolve my issue
of the CMYK values in the
On Mon, 28 Apr 2008 21:01:13 +0400
Alexandre Prokoudine [EMAIL PROTECTED] wrote:
Color management isn't fully implemented yet (previews will give you
wrong colors in plug-ins if you use AdobeRGB as working space profile,
too). No idea when this will be fixed.
To be honest, aside from the usual
On Mon, Apr 28, 2008 at 9:18 PM, Jon Senior wrote:
On Mon, 28 Apr 2008 21:01:13 +0400
Alexandre Prokoudine wrote:
Color management isn't fully implemented yet (previews will give you
wrong colors in plug-ins if you use AdobeRGB as working space profile,
too). No idea when this will be
Hi,
On Mon, 2008-04-28 at 21:01 +0400, Alexandre Prokoudine wrote:
Well. I compiled it with --enable-shared=no --enable-static=yes,
and it works fine. It seems slightly faster on some operations (Although
I could easily be imagining that), but sadly still doesn't resolve my issue
of the
Hi,
Sven Neumann wrote:
This may very well be a memory leak in Gimp-Perl. Have you run this in
valgrind with leak-check enabled? That should give you a good idea of
where the leak actually is.
This is the valgrind report:
==31947==
==31947== ERROR SUMMARY: 0 errors from 0 contexts
