Trying to install a tar.gz package on my 9.3 with KDE 3.5 I run into problems. Easiest of course is Kpackage manager because that would completely unpack the tar.gz. I may of course gzip the gz and tar the result but I like the kpackage. But when I try to unpack it I get: Unknown package type: /home/cons/HPLX/kio_hplx-0.3.tar.gz And this although kpackage is able to install tar.gz packages. Anybody know of a possibility to force the install?
On Thursday 23 February 2006 09:55, C. Brouerius van Nidek wrote:
Trying to install a tar.gz package on my 9.3 with KDE 3.5 I run into problems. Easiest of course is Kpackage manager because that would completely unpack the tar.gz. I may of course gzip the gz and tar the result but I like the kpackage. But when I try to unpack it I get:
Unknown package type: /home/cons/HPLX/kio_hplx-0.3.tar.gz
And this although kpackage is able to install tar.gz packages. Anybody know of a possibility to force the install?
Hello! I thought "KPackage" alluded to it being an rpm "package" management and installation tool comparable to Synaptic (works with apt.) I haven't tested it because I use command line rpm, apt and YaST for that. I also thought the usual procedure was to tar one's desired directories and files into a tarball and then compress it with either gzip or bzip, the former creating a convenient backup and the latter compressing. If you navigate to the file in Konqueror and click on it, an appropriate GUI program will be called up that can decompress and extract it's contents. Otherwise, a quick "man tar" in a shell should get you going. regards, Carl
On Thursday 23 February 2006 10:40 am, Carl Hartung wrote:
thought "KPackage" alluded to it being an rpm "package" management and installation tool comparable to Synaptic (works with apt.) I haven't tested it because I use command line rpm, apt and YaST for that. KPackage alludes to being an RPM, Debian, Slackware and BSD package manager.
The problem here is that the OP's tarball is probably not a valid package.
It is probably a source tarball where one needs to manually untar the
archive, configure, make and make install.
--
Jerry Feldman
Thursday, 23 February 2006 22:15 samaye, Jerry Feldman alekhiit:
The problem here is that the OP's tarball is probably not a valid package. It is probably a source tarball where one needs to manually untar the archive, configure, make and make install.
Some tarballs are not properly recognized by the GUI -- see my recent post on "Is there a bug with Ark". Try to decompress the tgz by using tar xvzf <filename> on the command line. -- Tux #395953 resides at http://samvit.org playing with KDE 3.51 on SUSE Linux 10.0 $ date [] CCE +2006-02-24 W08-5 UTC+0530
On Friday 24 February 2006 06:17, Shriramana Sharma wrote:
Thursday, 23 February 2006 22:15 samaye, Jerry Feldman alekhiit:
The problem here is that the OP's tarball is probably not a valid package. It is probably a source tarball where one needs to manually untar the archive, configure, make and make install.
Some tarballs are not properly recognized by the GUI -- see my recent post on "Is there a bug with Ark". Try to decompress the tgz by using tar xvzf <filename> on the command line.
Done the decompressing in /home and I read the README. According to the README I should install the package with ./configure then make and as root makeinstall. Started out with ./configure and after a long row of activities I get following information at the end: checking for rpath... yes checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix! No idea if and when which prefix I have chosen. What is meant with this sentence and how to proceed?
On 2/25/06, C. Brouerius van Nidek
On Friday 24 February 2006 06:17, Shriramana Sharma wrote:
Thursday, 23 February 2006 22:15 samaye, Jerry Feldman alekhiit:
The problem here is that the OP's tarball is probably not a valid package. It is probably a source tarball where one needs to manually untar the archive, configure, make and make install.
Some tarballs are not properly recognized by the GUI -- see my recent post on "Is there a bug with Ark". Try to decompress the tgz by using tar xvzf <filename> on the command line.
Done the decompressing in /home and I read the README. According to the README I should install the package with ./configure then make and as root makeinstall.
Started out with ./configure and after a long row of activities I get following information at the end:
checking for rpath... yes checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix!
No idea if and when which prefix I have chosen. What is meant with this sentence and how to proceed?
Normally, all required headers are installed with KDE. Invoking "kde-config --prefix" should return the basepath (prefix) of the KDE installation (i.e. /opt/kde3). If no prefix is specified "/usr/local" is used by default. You may combine the call to kde-config and configure: # ./configure --prefix=`kde-config --prefix` It should now find the headers successfully write a config file. \Steve
On Saturday 25 February 2006 19:28, Steve Graegert wrote: kde-config --prefix or the combination of ./configure --prefix=`kde-config --prefix First used the combination. Nothing happened. I then used kde-config and got a reply /opt/kde3 Then I used ./configure and got the same message as before. What went wrong? I also used ./configure --prefix=/opt/kde3 but the system still complaints that: checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix! Need surely your help to solve this one.
On 2/25/06, C. Brouerius van Nidek
On Saturday 25 February 2006 19:28, Steve Graegert wrote: kde-config --prefix or the combination of ./configure --prefix=`kde-config --prefix
First used the combination. Nothing happened. I then used kde-config and got a reply /opt/kde3 Then I used ./configure and got the same message as before. What went wrong? I also used ./configure --prefix=/opt/kde3 but the system still complaints that: checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix!
Need surely your help to solve this one.
Did you check that the headers exist in /opt/kde3? You should notice the existence of the "include" subdirectory: # ls `kde-config --prefix` . .. bin env include kdevbdb lib sbin share shutdown If the include directory is not present may have to install the kde3-devel package. Don't recall the exact name, nor do I really know if the headers are installed by default, but I think they are. \Steve
On Saturday 25 February 2006 21:08, Steve Graegert wrote:
bin env include kdevbdb lib sbin share shutdown
bin env include lib share shutdown are there. Missing kdevbdb sbin Must be the devel packages as Jos mentioned. And the advice to use checkinstall I have seen more and I am planning to use it. Thanks
C. Brouerius van Nidek wrote:
On Saturday 25 February 2006 19:28, Steve Graegert wrote: kde-config --prefix or the combination of ./configure --prefix=`kde-config --prefix
First used the combination. Nothing happened. I then used kde-config and got a reply /opt/kde3 Then I used ./configure and got the same message as before. What went wrong? I also used ./configure --prefix=/opt/kde3 but the system still complaints that: checking for KDE... configure: error: in the prefix, you've chosen, are no KDE headers installed. This will fail. So, check this please and use another prefix!
Need surely your help to solve this one.
"No headers installed" *always* means you are lacking some -devel- packages because they include the header files. So search in Yast with search string "kde" and install every -devel- packacge that shows up. And before I forget. Do yourself a favor and also install "checkinstall". Then don't do "make install" but "checkinstall". You get an rpm file that you can install with Yast and maintain system integrity. Regards, -- Jos van Kan registered Linux user #152704
participants (6)
-
C. Brouerius van Nidek -
Carl Hartung -
Jerry Feldman -
Jos van Kan -
Shriramana Sharma -
Steve Graegert