After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 20052 - Gimp-Perl should link against libs in source tree, not installed libs
Gimp-Perl should link against libs in source tree, not installed libs
Status: RESOLVED FIXED
Product: gimp-perl
Classification: Other
Component: General
unspecified
Other All
: Normal enhancement
: ---
Assigned To: gimp-perl bugs
gimp-perl bugs
Depends on:
Blocks:
 
 
Reported: 2000-08-07 06:46 UTC by Garrett LeSage
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Garrett LeSage 2001-01-28 15:56:42 UTC
Package: gimp
Version: CVS, Aug 06, 2000 (post-1.1.24)

Name........: Garrett LeSage
Email.......: garrett@linux.com
Platform....: Dual PIII/600 / 1G RAM, Debian GNU/Linux Woody
GIMP Version: CVS, Aug 06, 2000 (post-1.1.24)
GTK Version.: 1.2.8
WM/Version..: Sawfish 0.30.3-helix1


-- Other system notes:
Plenty of hard drive space; more than enough for Gimp + swap. Also tried launching the Gimp with a non-existant ~/.gimp-1.1 directory (to no avail).
--

-- Problem description:
Gimp starts to load just fine until it gets to the Perl plguins & scripts.

This is strange, as on the same system, 1.1.24 works fine (had to go back to non-CVS for daily usage).
--


-- How to repeat:
Every launch of Gimp compiled from CVS seems to be affected.
--


-- Other comments:
Moving all the Perl scripts (determined with file, utilizing cut and xargs) out of the plugins directory allows Gimp to start, however Perl-less. ):

Just for a matter of comparison, I compiled and installed the latest Gimp from CVS on a freshly installed desktop, one running a 2.2.x kernel (main workstation is using 2.4.x). The same peculiar problem arises.

It's strange that 1.1.24 works great on both -- Perl functioning and all and the CVS version is reliably _not_ working, thanks to Perl.
--




------- Additional Comments From mitch@convergence.de 2000-08-09 11:25:42 ----

Subject: [gimp-bug] "Hang" during splash screen; stalls on Perl scripts/plugins
From: Michael Natterer <mitch@convergence.de>
To: 20052@bugs.gnome.org
Cc: Marc Lehmann <pcg@goof.com>
Message-Id: <87snsesbgp.fsf@polaris.convergence.de>
Date: 09 Aug 2000 17:25:42 +0200

Hi Garret,

the problem is that gimp-perl compiles and links against the _installed_
version of libgimp, not against the one from the source.

So, every time a symbol is changed (moved to "compat" in this case),
you have to install libgimp, "make clean" in the perl directory and
compile it again :(

Marc, could you change the order of the library paths to fix this?

bye,
--Mitch




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-28 10:56 -------
This bug was previously known as bug 20052 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=20052
Originally filed under the gimp product and general component.

The original reporter (garrett@linux.com) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, egger@suse.de.

Comment 1 Raphaël Quinet 2001-04-26 18:11:52 UTC
Re-assigning all Gimp bugs to default component owner (Gimp bugs list)
Comment 2 Sven Neumann 2003-02-28 17:56:26 UTC
Marc Lehmann claims this has been fixed MANY years ago. Let's close it
then...
Comment 3 Raphaël Quinet 2003-06-20 18:49:28 UTC
The fix is part of the stable release 1.2.4 (or earlier).  Closing
this bug.
Comment 4 Dave Neary 2004-01-05 19:35:57 UTC
Re-assigning old gimp-perl bugs to gimp-perl product.
Comment 5 Dave Neary 2004-01-05 19:37:38 UTC
re-closing bugs that have already been resolved.