Hi,
Jeff Trefftzs [EMAIL PROTECTED] writes:
Does gimp-1.3.21 suddenly need fontconfig-2.2.0 or greater, where
gimp-1.3.20 didn't?
It turned out that GIMP-1.3.20 already needed it. It crashed on people
that tried to use it with earlier fontconfig versions. That's why we
added a compile time
On Thu, 2003-10-09 at 14:37, Sven Neumann wrote:
I have however no idea why you are having these problems when
upgrading. Perhaps someone more familiar with RedHat can shed some
light on this?
One can get fontconfig 2.2 from Red Hat Rawhide. It works fine on RH9.
I have added an example link
On Thu, 2003-10-09 at 07:31, Ville Ptsi wrote:
On Thu, 2003-10-09 at 14:37, Sven Neumann wrote:
I have however no idea why you are having these problems when
upgrading. Perhaps someone more familiar with RedHat can shed some
light on this?
One can get fontconfig 2.2 from Red Hat Rawhide.
On Thu, 2003-10-09 at 16:06, Tim Mooney wrote:
In regard to: Re: [Gimp-developer] gimp-1.3.21, fontconfig-2.2+ configure...:
You can't really rely on timestamps, since they will likely be preserved
by RPM (which uses cpio as the internal mechanism for packaging/transport).
The problem isn't
In regard to: Re: [Gimp-developer] gimp-1.3.21, fontconfig-2.2+ configure...:
On Thu, 2003-10-09 at 07:31, Ville Pätsi wrote:
On Thu, 2003-10-09 at 14:37, Sven Neumann wrote:
I have however no idea why you are having these problems when
upgrading. Perhaps someone more familiar with RedHat
On Wednesday 08 October 2003 2:43 pm, Jeff Trefftzs wrote:
Hi,
On Monday I downloaded the latest gimp-1.3.21, expecting to be able
to have a sparkling new version to play with by sometime that
afternoon. No such luck. I'm running into the following problem:
checking PANGOFT2_CFLAGS...
