On SUSE 9.1, checkinstall 1.6.0beta3. Using checkinstall I get an error message (see below). It seems that checkinstall cannot execute mkdir correctly when building the rpm. subsequently it does not recognise that the directory exists and aborts with error. Anyone knows why this happens? I assumed this was one of the central things checkinstall should be able to do? Kostas ----- /bin/sh ../../admin/mkinstalldirs /opt/kde3/share/doc/HTML/en/bpconf mkdir -p -- /opt/kde3/share/doc/HTML/en/bpconf /usr/bin/install -c -p -m 644 index.docbook /opt/kde3/share/doc/HTML/en/bpconf/index.docbook /usr/bin/install: preserving times for `/opt/kde3/share/doc/HTML/en/bpconf/index.docbook': No such file or directory /usr/bin/install: cannot set time stamps for `/opt/kde3/share/doc/HTML/en/bpconf/index.docbook': No such file or directory /usr/bin/install -c -p -m 644 bpconf.png /opt/kde3/share/doc/HTML/en/bpconf/bpconf.png /usr/bin/install: preserving times for `/opt/kde3/share/doc/HTML/en/bpconf/bpconf.png': No such file or directory /usr/bin/install: cannot set time stamps for `/opt/kde3/share/doc/HTML/en/bpconf/bpconf.png': No such file or directory /usr/bin/install -c -p -m 644 bpconf-feed.png /opt/kde3/share/doc/HTML/en/bpconf/bpconf-feed.png /usr/bin/install: preserving times for `/opt/kde3/share/doc/HTML/en/bpconf/bpconf-feed.png': No such file or directory /usr/bin/install: cannot set time stamps for `/opt/kde3/share/doc/HTML/en/bpconf/bpconf-feed.png': No such file or directory make[3]: *** [install-nls] Error 1 make[3]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc/en' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc/en' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc' make: *** [install-recursive] Error 1 **** Installation failed. Aborting package creation. Cleaning up...OK Bye.
On Thursday 03 March 2005 09:33, Konstantinos Georgokitsos wrote:
Using checkinstall I get an error message (see below). It seems that checkinstall cannot execute mkdir correctly when building the rpm. subsequently it does not recognise that the directory exists and aborts with error. Anyone knows why this happens? I assumed this was one of the central things checkinstall should be able to do?
See if you can do make install on it's own. It looks like that's failing. -- Kind regards Hans du Plooy SagacIT (Pty) Ltd hansdp at sagacit dot com
On Thursday 03 March 2005 09:49, Hans du Plooy wrote:
See if you can do make install on it's own. It looks like that's failing.
No, that is not failing: # make install Making install in doc make[1]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc' Making install in . make[2]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc' make[3]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc' make[2]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc' Making install in en make[2]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc/en' make[3]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc/en' make[3]: Nothing to be done for `install-exec-am'. /bin/sh ../../admin/mkinstalldirs /opt/kde3/share/doc/HTML/en/bpconf mkdir -p -- /opt/kde3/share/doc/HTML/en/bpconf /usr/bin/install -c -p -m 644 index.docbook /opt/kde3/share/doc/HTML/en/bpconf/index.docbook /usr/bin/install -c -p -m 644 bpconf.png /opt/kde3/share/doc/HTML/en/bpconf/bpconf.png /usr/bin/install -c -p -m 644 bpconf-feed.png /opt/kde3/share/doc/HTML/en/bpconf/bpconf-feed.png /bin/sh ../../admin/mkinstalldirs /opt/kde3/share/doc/HTML/en/bpconf /usr/bin/install -c -p -m 644 index.cache.bz2 /opt/kde3/share/doc/HTML/en/bpconf/ rm -f /opt/kde3/share/doc/HTML/en/bpconf/common ln -s /opt/kde3/share/doc/HTML/en/common /opt/kde3/share/doc/HTML/en/bpconf/common make[3]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc/en' make[2]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc/en' make[1]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/doc' Making install in po make[1]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/po' make[2]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/po' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/po' make[1]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/po' Making install in src make[1]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/src' make[2]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/src' /bin/sh ../admin/mkinstalldirs /opt/kde3/bin /bin/sh ../libtool --silent --mode=install /usr/bin/install -c -p bpconf /opt/kde3/bin/bpconf /bin/sh ../admin/mkinstalldirs /opt/kde3/share/icons/hicolor/16x16/apps /usr/bin/install -c -p -m 644 ./hi16-app-bpconf.png /opt/kde3/share/icons/hicolor/16x16/apps/bpconf.png /bin/sh ../admin/mkinstalldirs /opt/kde3/share/icons/hicolor/32x32/apps /usr/bin/install -c -p -m 644 ./hi32-app-bpconf.png /opt/kde3/share/icons/hicolor/32x32/apps/bpconf.png /bin/sh ../admin/mkinstalldirs /opt/kde3/share/mimelnk /usr/bin/install -c -p -m 644 rss+xml.desktop /opt/kde3/share/mimelnk/rss+xml.desktop /bin/sh ../admin/mkinstalldirs /opt/kde3/share/applnk/Utilities /usr/bin/install -c -p -m 644 bpconf.desktop /opt/kde3/share/applnk/Utilities/bpconf.desktop /bin/sh ../admin/mkinstalldirs /opt/kde3/share/apps/bpconf mkdir -p -- /opt/kde3/share/apps/bpconf /usr/bin/install -c -p -m 644 bpconfui.rc /opt/kde3/share/apps/bpconf/bpconfui.rc make[2]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/src' make[1]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5/src' make[1]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5' make[2]: Entering directory `/home/kongeo/Programs/bashpodder/bpconf-0.5' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5' make[1]: Leaving directory `/home/kongeo/Programs/bashpodder/bpconf-0.5'
Hans du Plooy wrote:
On Thursday 03 March 2005 09:33, Konstantinos Georgokitsos wrote:
Using checkinstall I get an error message (see below). It seems that checkinstall cannot execute mkdir correctly when building the rpm. subsequently it does not recognise that the directory exists and aborts with error. Anyone knows why this happens? I assumed this was one of the central things checkinstall should be able to do?
See if you can do make install on it's own. It looks like that's failing.
I see this problem often with the checkinstall in 9.2. You have to do a make install, then do checkinstall and "rpm -Uvh /usr/src/packages/RPMS/i386/<whatever.rpm>" to keep the rpm database honest. I haven't had a look to see what the differences are between the SuSE checkinstall and the original sources, but at 9.0 I installed the one I built from non-SuSE source and it always segfaulted. On Mandrake 10.1 I'm successfully using checkinstall-1.6.0 built from source. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and Keen Flyer =====ALMOST ALL LINUX USED HERE, Solaris 10 SPARC is just for play=====
On Thursday 03 March 2005 08:37, Sid Boyce wrote: <snip>
I see this problem often with the checkinstall in 9.2. You have to do a make install, then do checkinstall and "rpm -Uvh /usr/src/packages/RPMS/i386/<whatever.rpm>" to keep the rpm database honest. I haven't had a look to see what the differences are between the SuSE checkinstall and the original sources, but at 9.0 I installed the one I built from non-SuSE source and it always segfaulted. On Mandrake 10.1 I'm successfully using checkinstall-1.6.0 built from source.
Hi All, I think this solution is highly creative. Thanks for sharing it, Sid, you just made my day! I've got some projects on the back burner that I'm going to try this on. Before I do, I have to ask you if there are any downsides? Have you had occasions where this procedure has just gone horribly wrong? Or is it actually as straightforward as it appears? (fingers crossed) regards, - Carl -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/
participants (4)
-
Carl E. Hartung -
Hans du Plooy -
Konstantinos Georgokitsos -
Sid Boyce