[garrick@xxxxxxxxxxxxxxxxxxxxxxxx: failure with gimp 1.1.23 (was Re: [Bug #116288] configure fails withgimp 1.1.17)]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is really something that needs to be fixed in gimp.m4.  Gimp
developer folks, could you please check this?

------- Start of forwarded message -------
Date: Mon, 16 Oct 2000 11:06:18 -0700 (PDT)
From: Garrick James <garrick@xxxxxxxxxxxxxxxxxxxxxxxx>
To: Robert L Krawitz <rlk@xxxxxxxxxxxx>
Subject: failure with gimp 1.1.23 (was Re: [Bug #116288] configure fails
 withgimp 1.1.17)
In-Reply-To: <200010071242.IAA29571@xxxxxxxx>
Content-Type: TEXT/PLAIN; charset=US-ASCII

Sorry to bug you again about this, but I have found an honest bug in
configure for print-4.0.b[23].

I gave up on gimp 1.1.17 (as you said) and upgraded to gimp 1.1.23 (the
last one to use glib/gtk 1.2.7).

configure still did not work properly.  After digging around I found the
following chunk of C code in two places in configure:

#if GIMP_CHECK_VERSION(1,1,20)
GimpPlugInInfo
#else
GPlugInInfo
#endif
PLUG_IN_INFO =
{
  NULL,  /* init_proc */
  NULL,  /* quit_proc */
  NULL,  /* query_proc */
  NULL   /* run_proc */
};

The problem is that the definitions in question did not change until gimp
1.1.24 (not 1.1.20 as configure is testing for).  Gimp 1.1.20 - 1.1.23 all
use GPlugInInfo (I downloaded all the sources and checked).  Gimp 1.1.24
was the first to use GimpPlugInInfo.  Changing the version check from
1,1,20 to 1,1,24 makes everything work as it should.

After making the change, everything compiled and works wonderfully with
gimp 1.1.23.

If you haven't already, close the bug I opened (#116288) and, if possible,
make the above changes for print-4.0b3.

Thanks for a great printer driver for my old Epson Stylus Color!!

- -Garrick


On Sat, 7 Oct 2000, Robert L Krawitz wrote:

>    Date: Fri, 6 Oct 2000 19:43:18 -0700 (PDT)
>    From: Garrick James <garrick@xxxxxxxxxxxxxxxxxxxxxxxx>
>    Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
>    Thanks for such a prompted response.
> 
>    But, crap.  I'm screwed.  I cannot use gimp 1.0, as it doesn't have some
>    functionality which I (rather my wife) need.
> 
>    I really cannot upgrade, as the newer versions of gimp require gtk
>    1.2.8 and glib 1.2.8.  My linux distribution (Debian potato) includes
>    1.2.7 of both libs.  After digging through the glib and gtk docs/notes/etc
>    it is indicated that 1.2.8 is not binarily backward compatable with 1.2.7
>    for both libs.  There's no way I'm going to recomile my whole system from
>    scratch.  :-(
> 
> You don't need to.  You can have both versions installed concurrently.
> 
>    Do you have any idea what the two listed args to gimptool do?  Can you
>    provide me with sample output for both so I can try to hack up the
>    configure script for my system?
> 
> [2(rlk)||{!690}<rlkppp>/mnt1/images]
> $ gimptool --gimpdatadir
> /usr/local/Libraries/share/gimp/1.1
> [2(rlk)||{!691}<rlkppp>/mnt1/images]
> $ gimptool --gimpplugindir
> /usr/local/Libraries///gimp/1.1
> 
> However, the plugin itself may not compile; I think we blew back
> compatibility a while back, too (although there is back compatibility
> with gimp 1.0).
> 
> -- 
> Robert Krawitz <rlk@xxxxxxxxxxxx>      http://www.tiac.net/users/rlk/
> 
> Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
> Member of the League for Programming Freedom -- mail lpf@xxxxxxxxxxxx
> Project lead for The Gimp Print --  http://gimp-print.sourceforge.net
> 
> "Linux doesn't dictate how I work, I dictate how Linux works."
> --Eric Crampton
> 
------- End of forwarded message -------


[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux