15 Apr
2011
15 Apr
'11
8:23 p.m.
While the work with cmake continues I have been working with building 3.5.10 on newer
Slackware systems. Some of the effort will help Trinity, which is part of my goal. Such as
testing patches for libpng and KDE4 compatibility.
I found some preliminary patches for KDE4 compatibility and have expanded those quite a
bit. I will submit those patches to Trinity when I am confident the entire package set is
working, which will require several days or more of actual usage.
I've rebuilt the entire 3.5.10 package set except koffice. Everything works
wonderfully except when I use kdesu to open kate. That is the only problem I have noticed
so far. When I open kate through kdesu there are no icons in the toolbars. Usually that
indicates a problem with libpng.
I'm guessing that this problem might eventually hit Trinity too.
Indeed, when I run that command from a terminal I see oodles of messages like this:
kate: WARNING: Pixmap not found for mimetype text/plain
libpng warning: Application was compiled with png.h from libpng-1.4.3
libpng warning: Application is running with png.c from libpng-1.2.44
libpng error: Incompatible libpng version in application and library
So apparently kdebase (at least) linked to libpng 1.4.3 when compiling but oddly wants to
run using libpng 1.2.44.
Searching the web hasn't helped me nail the solution other than the obvious that there
is a conflict between the two versions.
I have two versions of libpng installed because that is the way Slackware is now bundled.
/usr/include/libpng12/*
/usr/include/libpng14/*
/usr/lib/libpng*
/usr/lib/pkgconfig/libpng12.pc
/usr/lib/pkgconfig/libpng14.pc
/usr/lib/pkgconfig/libpng.pc -> /usr/lib/pkgconfig/libpng14.pc
I'm thinking I should change the libpng.pc sym link from 1.4 to 1.2. I am hoping that
will force the packages to build with libpng 1.2. I'm going to try that but I thought
I'd post and see whether there might be something else I'm missing.
Oddly, I can open kate directly with my user account. I can log in to KDE as root and kate
behaves. I can open other apps with kdesu and there are no toolbar icon problems. I can
open konqueror with kdesu and then open a file from there with kate and the toolbar icons
are fine. I temporarily deleted all of root's related kate config files and saw the
same results.
I don't really care which version the packages link against as long as they all use
that same version after being installed.
Any ideas how to avoid these libpng conflicts?
Thanks.
Darrell
15 Apr
15 Apr
8:45 p.m.
New subject: [trinity-devel] libpng version conflicts
Fri, 15 Apr 2011 13:23:10 -0700 (PDT),
Darrell Anderson <humanreadable(a)yahoo.com> wrote :
[...]
kate: WARNING: Pixmap not found for mimetype text/plain
libpng warning: Application was compiled with png.h from libpng-1.4.3
libpng warning: Application is running with png.c from libpng-1.2.44
libpng error: Incompatible libpng version in application and library
So apparently kdebase (at least) linked to libpng 1.4.3 when
compiling but oddly wants to run using libpng 1.2.44.
Searching the web hasn't helped me nail the solution other than the
obvious that there is a conflict between the two versions.
I have two versions of libpng installed because that is the way
Slackware is now bundled.
/usr/include/libpng12/*
/usr/include/libpng14/*
/usr/lib/libpng*
/usr/lib/pkgconfig/libpng12.pc
/usr/lib/pkgconfig/libpng14.pc
/usr/lib/pkgconfig/libpng.pc -> /usr/lib/pkgconfig/libpng14.pc
I'm thinking I should change the libpng.pc sym link from 1.4 to 1.2.
I am hoping that will force the packages to build with libpng 1.2.
I'm going to try that but I thought I'd post and see whether there
might be something else I'm missing.
[...]
Any ideas how to avoid these libpng conflicts?
From the Slackbuilds.org mailing
list :
----
Wed, 9 Jun 2010 18:49:26 -0300,
Max Miorim <miorimmax(a)gmail.com> wrote :
Hi,
The following patches will fix libkate build (using libpng12) and make
the SlackBuild conform to the template.
As a side note, I have decided to use PNG_CFLAGS and PNG_LIBS instead
of writing a patch to the source itself or doing something like 'sed
-e "s#libpng#&12#g configure.ac && autoreconf -f -i' before the
'./configure'.
Also, this SlackBbuild got removed in
c0730536a1d3fdcdd0a8d00f637ce97246a0e42e, the patches will apply
cleanly on a revert of said commit.
-- Max
----
I attached the patches to this e-mail.
Thanks.
Darrell
10:16 p.m.
New subject: [trinity-devel] libpng version conflicts
--- On Fri, 4/15/11, /dev/ammo42 <mickeytintincolle(a)yahoo.fr> wrote:
From: /dev/ammo42 <mickeytintincolle(a)yahoo.fr>
Subject: Re: [trinity-devel] libpng version conflicts
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Friday, April 15, 2011, 3:45 PM
Fri, 15 Apr 2011 13:23:10 -0700
(PDT),
Darrell Anderson <humanreadable(a)yahoo.com>
wrote :
Thanks for the reply. I was quite confused for a while with the patches until I realized
we were discussing two different kates.
I was referring to Kate the advanced text editor, not the codec. :)
Anyway, there might be a simple fix. I ran configure --help on kdelibs and kdebase. For
both packages there is a configure option called --with-extra-includes.
Interestingly, kdelibs automatically links to libpng12 while kdebase does not. I'm
building a new kdebase package right now with
--with-extra-includes=/usr/include/libpng12.
I added a simple test in the kdebase build script:
if [ -d /usr/include/libpng12 ] && [ -d /usr/include/libpng14 ]; then
if [ "`readlink /usr/include/libpng | grep libpng14`" ]; then
EXTRA_INCLUDES="/usr/include/libpng12"
fi
fi
I'll report back in an hour or so with the results.
Darrell
[...]
kate: WARNING: Pixmap not found for mimetype
text/plain
libpng warning: Application was compiled with
png.h
from libpng-1.4.3
libpng warning: Application is running
with png.c from libpng-1.2.44
libpng error: Incompatible libpng version in
application and library
So apparently kdebase (at least) linked to libpng
1.4.3 when
compiling but oddly wants to run using libpng
1.2.44.
Searching the web hasn't helped me nail the solution
other than the
obvious that there is a conflict between the two
versions.
I have two versions of libpng installed because that
is the way
Slackware is now bundled.
/usr/include/libpng12/*
/usr/include/libpng14/*
/usr/lib/libpng*
/usr/lib/pkgconfig/libpng12.pc
/usr/lib/pkgconfig/libpng14.pc
/usr/lib/pkgconfig/libpng.pc ->
/usr/lib/pkgconfig/libpng14.pc
I'm thinking I should change the libpng.pc sym link
from 1.4 to 1.2.
I am hoping that will force the packages to build
with
libpng 1.2.
I'm going to try that but I thought I'd
post and see
whether there
might be something else I'm missing.
[...]
Any ideas how to avoid these libpng conflicts?
From the Slackbuilds.org mailing
list :
----
Wed, 9 Jun 2010 18:49:26 -0300,
Max Miorim <miorimmax(a)gmail.com>
wrote :
Hi,
The following patches will fix libkate build (using
libpng12) and make
the SlackBuild conform to the template.
As a side note, I have decided to use PNG_CFLAGS and
PNG_LIBS instead
of writing a patch to the source itself or doing
something like 'sed
-e "s#libpng#&12#g configure.ac
&&
autoreconf -f -i' before the
'./configure'.
Also, this SlackBbuild got removed in
c0730536a1d3fdcdd0a8d00f637ce97246a0e42e, the patches
will apply
cleanly on a revert of said commit.
-- Max
----
I attached the patches to this e-mail.
>
> Thanks.
>
> Darrell
16 Apr
16 Apr
12:55 a.m.
New subject: [trinity-devel] libpng version conflicts
I'll report back in an hour or so with the
results.
That was a wash. :( Same result.
Next I tried changing the various links to point to libpng12. ldd showed that kate built
with libpng12 and libpng14, but once again, no icons in the kate toolbars.
Only kate is affected by this. No other app.
I noticed every time I start kate that something deletes the user's kateui.rc file,
which would partially explain the lack of icons, although kate should revert to the
default kateui.rc file.
I suppose next I'll try deleting all libpng14 files.
Listening for ideas....
Darrell
7:48 a.m.
New subject: [trinity-devel] libpng version conflicts
Le Fri, 15 Apr 2011 17:55:53 -0700 (PDT),
Darrell Anderson <humanreadable(a)yahoo.com> a écrit :
Did you try setting PNG_CFLAGS / PNG_LIBS or using sed, as
the message
I quoted suggests ? I think sed would definitely prevent kate from
using libpng14 (or libpng12 if you want to force the use of libpng14).
But I'm not sure the libpng versions are really the problem, since you
said that without using kdesu there is no issue. Did you try running
Kate both with commandline sudo, su and su - ? If the results are not
the same, there are problems with environment variables.
I'll
report back in an hour or so with the results.
That was a wash. :( Same result.
Next I tried changing the various links to point to libpng12. ldd
showed that kate built with libpng12 and libpng14, but once again, no
icons in the kate toolbars.
Only kate is affected by this. No other app.
I noticed every time I start kate that something deletes the user's
kateui.rc file, which would partially explain the lack of icons,
although kate should revert to the default kateui.rc file.
I suppose next I'll try deleting all libpng14 files.
Listening for ideas....
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
3:46 p.m.
New subject: [trinity-devel] libpng version conflicts
--- On Sat, 4/16/11, /dev/ammo42 <mickeytintincolle(a)yahoo.fr> wrote:
From: /dev/ammo42 <mickeytintincolle(a)yahoo.fr>
Subject: Re: [trinity-devel] libpng version conflicts
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Saturday, April 16, 2011, 2:48 AM
Le Fri, 15 Apr 2011 17:55:53 -0700
(PDT),
Darrell Anderson <humanreadable(a)yahoo.com>
a écrit :
That was a wash. :( Same result.
Next I tried changing the various links to point to libpng12. ldd
I don't see any such flags such as PNG_CFLAGS / PNG_LIBS. I also never have seen a
separate build script for kate. The only place to set build flags is when building
kdebase.
I doubt the problem is related to kdesu ore nvironment variables. As I wrote previously, I
see the problem only with kate and not with any other app started through kdesu.
As I wrote previously, same problem with running from the command line. That is where I
see the error messages about the two different libpng versions.
I'm going to rebuild all packages with only one version of libpng installed. That will
eliminate that variable as a cause. That is not a smooth solution because many distros
install both versions of libpng. Trinity will have to address this problem sooner or
later.
> I'll report back in an hour or so with
the
results.
showed that kate built with libpng12 and
libpng14, but
once again, no
icons in the kate toolbars.
Only kate is affected by this. No other app.
I noticed every time I start kate that something
deletes the user's
kateui.rc file, which would partially explain the
lack
of icons,
although kate should revert to the default
kateui.rc
file.
I suppose next I'll try deleting all libpng14 files.
Listening for ideas....
Did you try setting PNG_CFLAGS / PNG_LIBS or using sed,
as
the message
I quoted suggests ? I think sed would definitely prevent
kate from
using libpng14 (or libpng12 if you want to force the use of
libpng14).
But I'm not sure the libpng versions are really the
problem, since you
said that without using kdesu there is no issue. Did you
try running
Kate both with commandline sudo, su and su - ? If the
results are not
the same, there are problems with environment variables.
>
> Darrell
>
>
5000
days inactive
5001
days old
5 comments
2 participants
participants (2)
-
/dev/ammo42 -
Darrell Anderson