Issue building Gimp from GIT

[Developers mailing list]

Hello, Everyone

I am running Fedora 30 and attempting to build, install & eventually run
GIMP from GIT. It builds & installs without error. But when I attempt to
run it I get the following:

[steve@afolkey2 bin]$ ./gimp-2.99
./gimp-2.99: error while loading shared libraries: libjson-c.so.2:
cannot open shared object file: No such file or directory

Obviously the error itself makes perfect sense. Fedora 30 has
libjson-c.so.4, not libjson-c.so.2

So the question is, why does GIMP compile and install with
libjson-c.so.2 not installed, but it won't run. I would assume that if a
file that GIMP requires if it is not going to crash is not present, that
GIMP would not compile. Also, what can I do to get this to work.

I know that I do not need to compile GIMP from GIT. I just enjoy doing
it. I further understand that the issue could be with Fedora 30 or me.

Thank you,

Steven P. Ulrick

_______________________________________________
gimp-developer-list mailing list
List address:    [hidden email]
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Developers mailing list]

On 7/3/19 8:59 PM, Steven P. Ulrick wrote:

> Hello, Everyone
>
> I am running Fedora 30 and attempting to build, install & eventually
> run GIMP from GIT. It builds & installs without error. But when I
> attempt to run it I get the following:
>
> [steve@afolkey2 bin]$ ./gimp-2.99
> ./gimp-2.99: error while loading shared libraries: libjson-c.so.2:
> cannot open shared object file: No such file or directory
>
> Obviously the error itself makes perfect sense. Fedora 30 has
> libjson-c.so.4, not libjson-c.so.2
>
> So the question is, why does GIMP compile and install with
> libjson-c.so.2 not installed, but it won't run. I would assume that if
> a file that GIMP requires if it is not going to crash is not present,
> that GIMP would not compile. Also, what can I do to get this to work.
>
> I know that I do not need to compile GIMP from GIT. I just enjoy doing
> it. I further understand that the issue could be with Fedora 30 or me.

Now I feel better. I just installed GIMP from the official Fedora 30
repos and it crashes with the same error:

[steve@afolkey2 ~]$ /usr/bin/gimp
/usr/bin/gimp: error while loading shared libraries: libjson-c.so.2:
cannot open shared object file: No such file or directory

I wonder if anyone else running Fedora 30 is having this issue.


Steven P. Ulrick

_______________________________________________
gimp-developer-list mailing list
List address:    [hidden email]
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Developers mailing list]

On July 4, 2019 4:59:10 AM GMT+02:00, "Steven P. Ulrick via gimp-developer-list" <[hidden email]> wrote:

>Hello, Everyone
>
>I am running Fedora 30 and attempting to build, install & eventually
>run
>GIMP from GIT. It builds & installs without error. But when I attempt
>to
>run it I get the following:
>
>[steve@afolkey2 bin]$ ./gimp-2.99
>./gimp-2.99: error while loading shared libraries: libjson-c.so.2:
>cannot open shared object file: No such file or directory
>
>Obviously the error itself makes perfect sense. Fedora 30 has
>libjson-c.so.4, not libjson-c.so.2
>
>So the question is, why does GIMP compile and install with
>libjson-c.so.2 not installed, but it won't run. I would assume that if
>a
>file that GIMP requires if it is not going to crash is not present,
>that
>GIMP would not compile. Also, what can I do to get this to work.

One of GIMP's dependencies was built against an older version of json-c.  Probably libmypaint, but you can find out using lddtree.  If you've built that dependency yourself as well (which is likely, otherwise we'd be hearing a lot more about it :) you need to rebuild it.

--
Ell
_______________________________________________
gimp-developer-list mailing list
List address:    [hidden email]
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Developers mailing list]

On 7/4/19 2:11 AM, Ell wrote:

> On July 4, 2019 4:59:10 AM GMT+02:00, "Steven P. Ulrick via
> gimp-developer-list" <[hidden email]> wrote:
> >Hello, Everyone
> >
> >I am running Fedora 30 and attempting to build, install & eventually
> >run
> >GIMP from GIT. It builds & installs without error. But when I attempt
> >to
> >run it I get the following:
> >
> >[steve@afolkey2 bin]$ ./gimp-2.99
> >./gimp-2.99: error while loading shared libraries: libjson-c.so
> <http://libjson-c.so>.2:
> >cannot open shared object file: No such file or directory
> >
> >Obviously the error itself makes perfect sense. Fedora 30 has
> >libjson-c.so <http://libjson-c.so>.4, not libjson-c.so
> <http://libjson-c.so>.2
> >
> >So the question is, why does GIMP compile and install with
> >libjson-c.so <http://libjson-c.so>.2 not installed, but it won't run.
> I would assume that if
> >a
> >file that GIMP requires if it is not going to crash is not present,
> >that
> >GIMP would not compile. Also, what can I do to get this to work.
>
> One of GIMP's dependencies was built against an older version of
> json-c. Probably libmypaint, but you can find out using lddtree. If
> you've built that dependency yourself as well (which is likely,
> otherwise we'd be hearing a lot more about it :) you need to rebuild it.

Yeah, under Fedora 27, I had to compile libmypaint from source to get
GIMP from GIT to build. Forgot all about it... Rebuilding now, having
made the appropriate changes to get the non-F30 version of libmypaint
out of the way. We'll see what happens.

The result is that the Fedora 30 version of GIMP starts perfectly. The
version from GIT, recompiled following a "make distclean", does not
work. It crashes with the same error.

_______________________________________________
gimp-developer-list mailing list
List address:    [hidden email]
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Developers mailing list]

On 7/4/19 3:59 AM, Steven P. Ulrick wrote:

> On 7/4/19 2:11 AM, Ell wrote:
>> On July 4, 2019 4:59:10 AM GMT+02:00, "Steven P. Ulrick via
>> gimp-developer-list" <[hidden email]> wrote:
>> >Hello, Everyone
>> >
>> >I am running Fedora 30 and attempting to build, install & eventually
>> >run
>> >GIMP from GIT. It builds & installs without error. But when I attempt
>> >to
>> >run it I get the following:
>> >
>> >[steve@afolkey2 bin]$ ./gimp-2.99
>> >./gimp-2.99: error while loading shared libraries: libjson-c.so
>> <http://libjson-c.so>.2:
>> >cannot open shared object file: No such file or directory
>> >
>> >Obviously the error itself makes perfect sense. Fedora 30 has
>> >libjson-c.so <http://libjson-c.so>.4, not libjson-c.so
>> <http://libjson-c.so>.2
>> >
>> >So the question is, why does GIMP compile and install with
>> >libjson-c.so <http://libjson-c.so>.2 not installed, but it won't
>> run. I would assume that if
>> >a
>> >file that GIMP requires if it is not going to crash is not present,
>> >that
>> >GIMP would not compile. Also, what can I do to get this to work.
>>
>> One of GIMP's dependencies was built against an older version of
>> json-c. Probably libmypaint, but you can find out using lddtree. If
>> you've built that dependency yourself as well (which is likely,
>> otherwise we'd be hearing a lot more about it :) you need to rebuild it.
>
>
> Yeah, under Fedora 27, I had to compile libmypaint from source to get
> GIMP from GIT to build. Forgot all about it... Rebuilding now, having
> made the appropriate changes to get the non-F30 version of libmypaint
> out of the way. We'll see what happens.
>
> The result is that the Fedora 30 version of GIMP starts perfectly. The
> version from GIT, recompiled following a "make distclean", does not
> work. It crashes with the same error.

Hello, Ell

Spoke to soon. I logged out, logged back in and tried again, and it
finally started. Strange, since I did "su - steve" in a terminal
directly before I tried starting GIMP from GIT. In any even, I can begin
rotating pictures from our recent trip to England...

Thank you for you help!

Steven P. Ulrick

_______________________________________________
gimp-developer-list mailing list
List address:    [hidden email]
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Liam R E Quin]

On Thu, 2019-07-04 at 04:04 -0500, Steven P. Ulrick via gimp-developer-
list wrote:
>
> Spoke to soon. I logged out, logged back in and tried again, and it
> finally started.


It sounds like you might be installing gimp and its depndencies into
somewhere owned by the operating system; /usr/local is probably safe on
Fedora (it isn't on Debian) but using a prefix like $HOME/opt is
better. Then put a short shell script in your PATH that runs your local
version gimp (mine is called "lgimp" for local gimp).


> begin
> rotating pictures from our recent trip to England...
I hope you had a good trip! Do you post pictures somewhere? :)

Liam (originally from the UK)


--
Liam Quin - web slave for https://www.fromoldbooks.org/
with fabulous vintage art and fascinating texts to read.
Click here to have the slave beaten.

_______________________________________________
gimp-developer-list mailing list
List address:    [hidden email]
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list