Running Gimp 2.4.x and 2.5.0 side by side

[Jon Senior]

Sorry if this is the wrong list for this question, but I figure the developers are most likely to be doing this.

I've followed the instructions on the site. BABL, GEGL and Gimp are all installed to /usr/local/gimp2.5. I've installed a modified version of the suggested wrapper script (with the correct paths) in /usr/local/bin.

Any attempt to run gimp-2.5 results in the message

------
Libgimp version mismatch!

The GIMP binary cannot run with a libgimp version
other than its own. This is GIMP 2.5.0, but the
libgimp version is 2.4.5.

Maybe you have GIMP versions in both /usr and /usr/local ?
------

I've tried carrying out the functions of the wrapper by hand. I've run ldconfig -N on the .../gimp-2.5/lib directory.

I'm using stow to manage the system so I could theoretically just use it to swap the versions in and out, but I'd rather be able to run them properly side-by-side.

Any suggestions?

--
Jon Senior <jon@...>
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Omari Stephens-2]

Jon Senior wrote:

> Sorry if this is the wrong list for this question, but I figure the developers are most likely to be doing this.
>
> I've followed the instructions on the site. BABL, GEGL and Gimp are all installed to /usr/local/gimp2.5. I've installed a modified version of the suggested wrapper script (with the correct paths) in /usr/local/bin.
>
> Any attempt to run gimp-2.5 results in the message
>
> ------
> Libgimp version mismatch!
>
> The GIMP binary cannot run with a libgimp version
> other than its own. This is GIMP 2.5.0, but the
> libgimp version is 2.4.5.
>
> Maybe you have GIMP versions in both /usr and /usr/local ?
> ------

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
`ldd /path/to/gimp2.5/bin/gimp`
and
`ldd --library-path /path/to/gimp2.5/lib /path/to/gimp2.5/bin/gimp`

Note that you can check for sure if this might be the problem by running
gimp2.5 directly with the overridden library path
`/lib/ld-2.7.so --library-path /path/to/gimp2.5/lib
/path/to/gimp2.5/bin/gimp`

cheers,
--xsdg
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Jon Senior]

On Mon, 28 Apr 2008 00:01:45 +0000
xsdg <xsdg@...> 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 I've tried doing it by hand as well.

> `ldd /path/to/gimp2.5/bin/gimp`
> and
> `ldd --library-path /path/to/gimp2.5/lib /path/to/gimp2.5/bin/gimp`

ldd reports it linking to /usr/local/lib, so confirming that it's missing the target! My version of glibc is 2.3.6 according to ldconfig --version and my version of ldd doesn't have the --library-path option.

> Note that you can check for sure if this might be the problem by running
> gimp2.5 directly with the overridden library path
> `/lib/ld-2.7.so --library-path /path/to/gimp2.5/lib
> /path/to/gimp2.5/bin/gimp`

I tried that and it still produced the same error. There's something going on in the linking stage of gimp I think. I'll try building static libraries only and see if that does it.

--
Jon Senior <jon@...>
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Jon Senior]

On Mon, 28 Apr 2008 00:01:45 +0000
xsdg <xsdg@...> 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 colour sampler being calculated differently from Photoshop, making it hard to follow Lee Varis' advice on obtaining good skin tones.

Thanks for your help. Looking forward to the final release, and I'll continue to play with 2.5 for testing purposes.

--
Jon Senior <jon@...>
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Alexandre Prokoudine]

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 colour sampler being calculated differently
> from Photoshop, making it hard to follow Lee Varis' advice on obtaining
> good skin tones.

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.

Alexandre
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Jon Senior]

On Mon, 28 Apr 2008 21:01:13 +0400
"Alexandre Prokoudine" <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 fixed.

To be honest, aside from the usual desire for adjustment layers (or something similar), my only real wish at the minute would be that the CMYK values that are generated in the Sample Points window matched those of PS. Or that I could choose the rendering algorithm. Is this something that will appear naturally as a part of the colour management, or is it a separate issue (C is not my forte, or I'd dive in and find out for myself!)?

--
Jon Senior <jon@...>
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Alexandre Prokoudine]

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 fixed.
>
>  To be honest, aside from the usual desire for adjustment layers (or something
> similar), my only real wish at the minute would be that the CMYK values that are
> generated in the Sample Points window matched those of PS. Or that I could
> choose the rendering algorithm. Is this something that will appear naturally as a
> part of the colour management, or is it a separate issue (C is not my forte, or I'd
> dive in and find out for myself!)?

This is probably something that should be discussed in a separate thread.

Making all related widgets color managed is the plan. If you are
willing to spend some time on doing this, I'm sure you help will be
very much appreciated. I also can't comment on technical side, but
someone like Sven who did most of work on initial CMM support can :)

Alexandre
_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Sven Neumann]

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 CMYK values in the colour sampler being calculated differently
> > from Photoshop, making it hard to follow Lee Varis' advice on obtaining
> > good skin tones.
>
> 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.

The preview of plug-ins has absolutely nothing to do with the RGB ->
CMYK conversion of the Color Picker tool. Why are you mentioning this
here?


Sven


_______________________________________________
Gimp-developer mailing list
Gimp-developer@...
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer