Stephan Hegel wrote:
> I fixed this by installing gimp-2.3 completely under /usr/local/Gimp-2.3
> and calling it by a little wrapper named gimpdev:
The release notes suggest to use /opt/gimp-2.3, BTW.
HTH,
Michael
--
GIMP > http://www.gimp.org | IRC: irc://irc.gimp.org/gimp
Wiki
Hi,
Does this affect the functionality of gimp-2.3 ? In that case
"configure" should not allow a "--prefix=/usr/local/Gimp-2.3".
And: it does not fix the problem what was mentioned on top of
the thread. HTH ? No, it does not help at all.
Regards,
Stephan.
Michael Schumacher wrote:
> Stephan
Stephan Hegel wrote:
> Does this affect the functionality of gimp-2.3 ? In that case
> "configure" should not allow a "--prefix=/usr/local/Gimp-2.3".
configure allows everything. Anyone who is building from source ought to
know that the prefix he chooses should be one that does not cause harm
to
I used the 2.3.11 version without problems
maybe you should try building the 2.3.12 version (current developement
release) with prefix (i'm using /opt/gimp-2.3)
also don't forget to create the script which lauches gimp
-->
#!/bin/sh
PATH=/opt/gimp-2.3/bin:$PATH
export PATH
LD_LIBRARY_PATH=/opt
Michael Schumacher wrote:
> You mean a GIMP 2.3 build with --prefix=/opt/gimp-2.3 still exhibits the
> same error on Slackware? Maybe this is something a Slackware user should
> investigate then.
Even on my SuSE 10.0, this would cause the same problem as LD_LIBRARY_PATH
does not point to "/opt/gimp
