Upgrading Slackware 7.1 to KDE-2.2.2

Upgrading Slackware 7.1 to KDE-2.2.2

Post by Tom Cra » Sun, 03 Mar 2002 07:37:11



Dear All,
        I am upgrading KDE on a Slackware 7.1 Linux system to KDE-2.2.2 and
have come across the following problem, compiling kpackage in kdeadmin;

make[3]: Entering directory `/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2/kpackage'
/bin/sh ../libtool --mode=link --tag=CXX g++  -O2 -fno-exceptions
-fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST   -o
kpackage -L/usr/X11/lib -L/usr/local/qt-2.3.1/lib -L/opt/kde2/lib  -L/usr/lib
-R /opt/kde2/lib -R /usr/local/qt-2.3.1/lib -R /usr/X11/lib TEPty.o kpackage.o
managementWidget.o packageDisplay.o packageProperties.o findf.o search.o
options.o pkgOptions.o packageInfo.o cache.o main.o utils.o kio.o
debInterface.o debDpkgInterface.o debAptInterface.o updateLoc.o procbuf.o
kplview.o pkgInterface.o rpmInterface.o kissInterface.o slackInterface.o
fbsdInterface.o rpmInstall.o rpmVerify.o rpmutils.o rpmMessages.o kpPty.o
kpTerm.o kpackage_meta_unload.o  -lkfile -ldb1  -lrpmbuild     -lrpm  -lpopt
-lz  
g++ -O2 -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT
-DQT_NO_ASCII_CAST -o kpackage TEPty.o kpackage.o managementWidget.o
packageDisplay.o packageProperties.o findf.o search.o options.o pkgOptions.o
packageInfo.o cache.o main.o utils.o kio.o debInterface.o debDpkgInterface.o
debAptInterface.o updateLoc.o procbuf.o kplview.o pkgInterface.o rpmInterface.o
kissInterface.o slackInterface.o fbsdInterface.o rpmInstall.o rpmVerify.o
rpmutils.o rpmMessages.o kpPty.o kpTerm.o kpackage_meta_unload.o
-L/usr/X11/lib -L/usr/local/qt-2.3.1/lib -L/opt/kde2/lib -L/usr/lib
/opt/kde2/lib/libkfile.so /opt/kde2/lib/libksycoca.so /opt/kde2/lib/libkio.so
-L/usr/X11R6/lib -L/usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66
-L/usr/i386-slackware-linux/lib /opt/kde2/lib/libkdesu.so -lutil
/opt/kde2/lib/libkssl.so /opt/kde2/lib/libkdeui.so /opt/kde2/lib/libkdecore.so
-ldl /opt/kde2/lib/libDCOP.so -lqt -lpng -ljpeg -lXext -lX11 -lSM -lICE
-lstdc++ -lm -lc -lgcc -ldb1 -lrpmbuild -lrpm -lpopt -lz -Wl,--rpath
-Wl,/opt/kde2/lib -Wl,--rpath -Wl,/opt/kde2/lib -Wl,--rpath
-Wl,/usr/local/qt-2.3.1/lib -Wl,--rpath -Wl,/usr/X11/lib
/usr/lib/librpm.a(messages.o): In function `rpmMessage':
messages.o(.text+0x50): multiple definition of `rpmMessage'
rpmMessages.o(.text+0x50): first defined here
/usr/i386-slackware-linux/bin/ld: Warning: size of symbol `rpmMessage' changed from 194 to 467 in messages.o
/usr/lib/librpm.a(query.o)(.data+0x25c): multiple definition of `specedit'
rpmMessages.o(.data+0x4): first defined here
/usr/lib/librpm.a(url.o): In function `ufdClose':
url.o(.text+0xa38): multiple definition of `ufdClose'
rpmMessages.o(.text+0x120): first defined here
/usr/i386-slackware-linux/bin/ld: Warning: size of symbol `ufdClose' changed from 13 to 64 in url.o
/usr/lib/librpm.a(url.o): In function `ufdOpen':
url.o(.text+0xa78): multiple definition of `ufdOpen'
rpmMessages.o(.text+0x130): first defined here
/usr/i386-slackware-linux/bin/ld: Warning: size of symbol `ufdOpen' changed from 59 to 294 in url.o
collect2: ld returned 1 exit status
make[3]: *** [kpackage] Error 1
make[3]: Leaving directory `/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2/kpackage'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2/kpackage'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2'
make: *** [all-recursive-am] Error 2

Searching groups.google.com I found a report of the same problem under
Slackware 7.0 plus a hack solution involving unpacking a Redhat rpm for the rpm
utility, repackaging as a Slackware tarball and installing that. After that it
needed buildrpm. Unfortunately I could not get this scheme to work on Slackware
7.1 :(.

Next I tried downloading the source for the rpm util and building that. Trouble
is, that needs the Berkeley DB program, which wanted other dependencies not on
my system. :-{

How have other Slackware 7.1 users coped with this KDE upgrade? Are the any
relatively painless methods of getting round this one?

Thanks
Tom (the impatient)

Should it have any bearing on this problem here are my system's library etc.
details.

bash-2.04# ver_linux
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux mklab 2.4.16 #3 Wed Feb 27 21:33:59 GMT 2002 i586 unknown
Kernel modules         2.3.11
Gnu C                  egcs-2.91.66
Binutils               2.9.1.0.25
Linux C Library        1.3.so
Dynamic Linker (ld.so) 1.9.9
ls: /usr/lib/libg++.so: No such file or directory
Procps                 2.0.6
Mount                  2.11n
Net-tools              (2000-05-21)
Kbd                    0.99
Sh-utils               2.0
Sh-utils               Parker.
Sh-utils              
Sh-utils               Inc.
Sh-utils               NO
Sh-utils               PURPOSE.

--
Tom Crane, Dept. Physics, Royal Holloway, University of London, Egham Hill,
Egham, Surrey, TW20 0EX, England.

SPAN:   19.875
Fax:    +44 (0) 1784 472794

 
 
 

Upgrading Slackware 7.1 to KDE-2.2.2

Post by Michael Parmele » Sun, 03 Mar 2002 10:46:38


Tom,

What version of KDE are you running now? I never could get my Slack 7.x to
upgrade to KDE 2. Using Google I did find a couple of pages from people who
actually accomplished it but even those people said it was a "painful"
process.

I didn't feel like messing with it so I upgraded to Slack 8 and then when
KDE 2.2.2 came out I had no problem getting it to install. (I used the .tgz
packages instead of compiling from source).

I wish I still had the link to the page from the guy who did successfully
upgrade his Slack 7.x to KDE 2.x. since I could give it to you. However,
with a little searching on Google you should be able to find it (if it is
still up).

good luck!
mike p.


> Dear All,
> I am upgrading KDE on a Slackware 7.1 Linux system to KDE-2.2.2 and
> have come across the following problem, compiling kpackage in kdeadmin;

> make[3]: Entering directory

`/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2/kpackage'
Quote:> /bin/sh ../libtool --mode=link --tag=CXX g++  -O2 -fno-exceptions
> -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST   -o
> kpackage -L/usr/X11/lib -L/usr/local/qt-2.3.1/lib -L/opt/kde2/lib
> -L/usr/lib -R /opt/kde2/lib -R /usr/local/qt-2.3.1/lib -R /usr/X11/lib
> TEPty.o kpackage.o managementWidget.o packageDisplay.o packageProperties.o
> findf.o search.o options.o pkgOptions.o packageInfo.o cache.o main.o
> utils.o kio.o debInterface.o debDpkgInterface.o debAptInterface.o
> updateLoc.o procbuf.o kplview.o pkgInterface.o rpmInterface.o
> kissInterface.o slackInterface.o fbsdInterface.o rpmInstall.o rpmVerify.o
> rpmutils.o rpmMessages.o kpPty.o
> kpTerm.o kpackage_meta_unload.o  -lkfile -ldb1  -lrpmbuild     -lrpm
> -lpopt -lz
> g++ -O2 -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT
> -DQT_NO_ASCII_CAST -o kpackage TEPty.o kpackage.o managementWidget.o
> packageDisplay.o packageProperties.o findf.o search.o options.o
> pkgOptions.o packageInfo.o cache.o main.o utils.o kio.o debInterface.o
> debDpkgInterface.o debAptInterface.o updateLoc.o procbuf.o kplview.o
> pkgInterface.o rpmInterface.o kissInterface.o slackInterface.o
> fbsdInterface.o rpmInstall.o rpmVerify.o rpmutils.o rpmMessages.o kpPty.o
> kpTerm.o kpackage_meta_unload.o -L/usr/X11/lib -L/usr/local/qt-2.3.1/lib
> -L/opt/kde2/lib -L/usr/lib /opt/kde2/lib/libkfile.so
> /opt/kde2/lib/libksycoca.so /opt/kde2/lib/libkio.so -L/usr/X11R6/lib
> -L/usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66
> -L/usr/i386-slackware-linux/lib /opt/kde2/lib/libkdesu.so -lutil
> /opt/kde2/lib/libkssl.so /opt/kde2/lib/libkdeui.so
> /opt/kde2/lib/libkdecore.so -ldl /opt/kde2/lib/libDCOP.so -lqt -lpng
> -ljpeg -lXext -lX11 -lSM -lICE -lstdc++ -lm -lc -lgcc -ldb1 -lrpmbuild
> -lrpm -lpopt -lz -Wl,--rpath -Wl,/opt/kde2/lib -Wl,--rpath
> -Wl,/opt/kde2/lib -Wl,--rpath -Wl,/usr/local/qt-2.3.1/lib -Wl,--rpath
> -Wl,/usr/X11/lib /usr/lib/librpm.a(messages.o): In function `rpmMessage':
> messages.o(.text+0x50): multiple definition of `rpmMessage'
> rpmMessages.o(.text+0x50): first defined here
> /usr/i386-slackware-linux/bin/ld: Warning: size of symbol `rpmMessage'
> changed from 194 to 467 in messages.o
> /usr/lib/librpm.a(query.o)(.data+0x25c): multiple definition of `specedit'
> rpmMessages.o(.data+0x4): first defined here /usr/lib/librpm.a(url.o): In
> function `ufdClose': url.o(.text+0xa38): multiple definition of `ufdClose'
> rpmMessages.o(.text+0x120): first defined here
> /usr/i386-slackware-linux/bin/ld: Warning: size of symbol `ufdClose'
> changed from 13 to 64 in url.o /usr/lib/librpm.a(url.o): In function
> `ufdOpen': url.o(.text+0xa78): multiple definition of `ufdOpen'
> rpmMessages.o(.text+0x130): first defined here
> /usr/i386-slackware-linux/bin/ld: Warning: size of symbol `ufdOpen'
> changed from 59 to 294 in url.o collect2: ld returned 1 exit status
> make[3]: *** [kpackage] Error 1 make[3]: Leaving directory

`/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2/kpackage'
Quote:> make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory

`/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2/kpackage'

- Show quoted text -

Quote:> make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory
> `/tmp/kde/download.us.kde.org/pub/kde/stable/2.2.2/src/kdeadmin-2.2.2'
> make: *** [all-recursive-am] Error 2

> Searching groups.google.com I found a report of the same problem under
> Slackware 7.0 plus a hack solution involving unpacking a Redhat rpm for
> the rpm utility, repackaging as a Slackware tarball and installing that.
> After that it needed buildrpm. Unfortunately I could not get this scheme
> to work on Slackware 7.1 :(.

> Next I tried downloading the source for the rpm util and building that.
> Trouble is, that needs the Berkeley DB program, which wanted other
> dependencies not on my system. :-{

> How have other Slackware 7.1 users coped with this KDE upgrade? Are the
> any relatively painless methods of getting round this one?

> Thanks
> Tom (the impatient)

> Should it have any bearing on this problem here are my system's library
> etc. details.

> bash-2.04# ver_linux
> -- Versions installed: (if some fields are empty or looks
> -- unusual then possibly you have very old versions)
> Linux mklab 2.4.16 #3 Wed Feb 27 21:33:59 GMT 2002 i586 unknown
> Kernel modules         2.3.11
> Gnu C                  egcs-2.91.66
> Binutils               2.9.1.0.25
> Linux C Library        1.3.so
> Dynamic Linker (ld.so) 1.9.9
> ls: /usr/lib/libg++.so: No such file or directory
> Procps                 2.0.6
> Mount                  2.11n
> Net-tools              (2000-05-21)
> Kbd                    0.99
> Sh-utils               2.0
> Sh-utils               Parker.
> Sh-utils
> Sh-utils               Inc.
> Sh-utils               NO
> Sh-utils               PURPOSE.


 
 
 

Upgrading Slackware 7.1 to KDE-2.2.2

Post by Damian Walke » Tue, 19 Mar 2002 06:15:50



Quote:> What version of KDE are you running now? I never could get my Slack 7.x to
> upgrade to KDE 2. Using Google I did find a couple of pages from people
> who actually accomplished it but even those people said it was a "painful"
> process.

I'm running Slackware 7.1 with KDE 2.2.2.  But the way I got it to compile
was a gross bodge.  First I did a ./configure as normal.  Then before the
make, or after the make failed (both work fine) I edited the makefile, and
removed 'kpackage' from the line begining "TOPSUBDIRS =".  This if course
means I can't use kpackage, but since I don't tend to use RPMs here, that
was fine by me.  Then everything else compiled fine afterwards.  It's not
an ideal solution but as no better answers have appeared since your post, I
thought I might as well give this one.

The bodge was successful here at least.  There are a few things that don't
appear to work properly, but none of them have anything to do with package
handling and I'm gradually working my way through them in the order that
they most irritate me.

--
Damian - http://damian.snigfarp.karoo.net/ - UPDATED 12/3/2002
(for email replies, my name is "damian", not "nospam")

 
 
 

1. kde 2.2 upgrade on Redhat 7.1 linux

I am having a tough time upgrading KDE fro 2.1 to 2.2.   After a helpful
suggestion from one of the users, I was able to obtain additonal libraries
like 'libxml...' 'libfam..' etc
from rpmfind.net  and install them

Every time I tried to upgrade a package, It complains about a dependency on
a different package.  Till now I have downloaded and installed around 10
additional packages.

Any easy way of doing this.

Has anyone succesfully upgraded KDE 2.2 on RH 7.1

Thanks in advance...

Z

2. lpr and lpd does talk to each other

3. GLIBC 2.2 - Slackware 7.1

4. NO BS!

5. KDE 2.2 on SuSE 7.1/PPC

6. Problems compiling with gcc- "ld: cannot open crt1.o: No such file or directory"

7. KDE 2.2 & Redhat 7.1 - Install problem

8. ip forwarding

9. KDE 2.2 RPMS for RH 7.1

10. Upgrading KDE 2.2-11 to KDE 3.0.3

11. Should I upgread to kde-3.0 from kde-2.2.2 on Suse-7.3 ?

12. Sound with non KDE apps within KDE-2.2.2

13. Problem installing KDE (source or binary) on slackware 7.1