"Darrell Anderson" humanreadable@yahoo.com pisze:
--- On Sat, 4/16/11, /dev/ammo42 wrote:
From: /dev/ammo42 Subject: Re: [trinity-devel] libpng version conflicts To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, April 16, 2011, 2:48 AM Le Fri, 15 Apr 2011 17:55:53 -0700 (PDT), Darrell Anderson a écrit :
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....
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
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 have no problems with kate under kdesu. I've compiled kde3 on slackware-13.1 and -current using default slackware's libpng. Did you recompile qt-3 before building kde? What were your configure options? I used qt3 slackbuild from slackware12.2 and changed "-qt-libpng" to "-system-libpng". Take a look at "KDE 3.5.10 for slackware-13.1" thread on linuxquesions.org to check which patches i used.
Regards,
alekow
------------------------------------------------- Pobierz darmowy program PIT. Kliknij tutaj >> http://linkint.pl/f296d
I have no problems with kate under kdesu. I've compiled kde3 on slackware-13.1 and -current using default slackware's libpng. Did you recompile qt-3 before building kde? What were your configure options? I used qt3 slackbuild from slackware12.2 and changed "-qt-libpng" to "-system-libpng". Take a look at "KDE 3.5.10 for slackware-13.1" thread on linuxquesions.org to check which patches i used.
Regards,
alekow
Yes, I'm using "-system-libpng."
No longer a problem. I don't know the original cause. I deleted all packages, did some minor house cleaning in my build environment, and rebuilt the packages. No more toolbar icon problems with Kate.
The only noticeable problem is Amarok does not build properly in 13.1. The locale and HTML help files do not compile into the package. The packages builds as expected in 12.2 using the same build script. I need to fix that because my build scripts are available to anybody who visits my web site.
Darrell
-
alekow -
Darrell Anderson