LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-01-2013, 02:14 AM   #16
vdemuth
Member
 
Registered: Oct 2003
Location: West Midlands, UK
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
Posts: 770

Rep: Reputation: 94

Fails at the very end with this error

Code:
-- Installing: /tmp/build/package-digikam/usr/share/locale/zh_TW/LC_MESSAGES/kipiplugin_advancedslideshow.mo
-- Installing: /tmp/build/package-digikam/usr/share/locale/zh_TW/LC_MESSAGES/kipiplugin_flashexport.mo
-- Installing: /tmp/build/package-digikam/usr/share/locale/zh_TW/LC_MESSAGES/kipiplugin_gpssync.mo
-- Installing: /tmp/build/package-digikam/usr/share/locale/zh_TW/LC_MESSAGES/libkipi.mo
-- Installing: /tmp/build/package-digikam/usr/share/locale/zh_TW/LC_MESSAGES/kipiplugin_metadataedit.mo
-- Installing: /tmp/build/package-digikam/usr/share/locale/zh_TW/LC_MESSAGES/kipiplugin_batchprocessimages.mo
cat: /home/xxx/Downloads/digikam/digikam.SlackBuild: No such file or directory
That's another 3 hours I'll never get back again.

Please don't take this the wrong way as I have a great deal of both sympathy and admiration for those who have the time to build from source, including sharing their findings with the wider user base, so many thanks for that.
But I've just grabbed the wifes lappy, and the whole process has taken less than 10 minutes thanks to dependency resolution and a much more widely tested software repository, so am currently using that for my photo management and being able to use the computer for what it's designed for rather than spend hours unproductively waiting for compiling/building only to see it fail is almost pushing me to another distro after more than 8 years of using Slackware. So frustrating that it should all be so difficult and long winded in the 21st century.
 
Old 04-01-2013, 02:27 AM   #17
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,617

Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
By any chance, did you rename the digikam.SlackBuild to another name?
 
Old 04-01-2013, 03:49 AM   #18
Bazzaah
Member
 
Registered: Mar 2007
Distribution: Slackware64-current, Slackware64 14
Posts: 327

Original Poster
Rep: Reputation: 49
I have found that installations of Digikam and Amarok have failed if I use 'sudo make install' for example instead of 'su' then 'make install'.
 
Old 04-01-2013, 04:11 AM   #19
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,617

Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
If you use slackbuilds, it's supposed to be run using su or su - not sudo
 
Old 04-01-2013, 04:46 AM   #20
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,495

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
I think he builds and installs directly from source (and I'm wondering how he manages to remove old stuff when he needs to upgrade).

Last edited by ponce; 04-01-2013 at 04:47 AM.
 
Old 04-01-2013, 06:13 AM   #21
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,626

Rep: Reputation: 142Reputation: 142
Quote:
Originally Posted by willysr View Post
By any chance, did you rename the digikam.SlackBuild to another name?
Just guessing based on my own experience, but still hoping it helps vdemuth to track the problem down.

In my experience 9 out of ten such problems are caused by wrong file access mode or user privileges. Just guessing, but did you take into account that digikam.SlackBuild is one of the following?

1. It is readable and has to be called this way:
Code:
$ su -c "sh digikam.SlackBuild"
OR that it is

2. It is readable and executable and thus can alternatively called like so:
Code:
su -c "./digikam.SlackBuild"
Sometimes obsolete stuff in /tmp may cause trouble, so ensure to wipe all stuff related to building digikam from there. Finally, I occasionally had problems on multilib systems, when the build script picked 32-bit libraries, although it was supposed to pick 64-bit stuff. In the last case the only reliable (!) workaround I found was to build the package on a pure 64-bit system and transfer the binary package to the target machine.

gargamel
 
Old 04-01-2013, 06:15 AM   #22
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,626

Rep: Reputation: 142Reputation: 142
Quote:
Originally Posted by ponce View Post
I think he builds and installs directly from source (and I'm wondering how he manages to remove old stuff when he needs to upgrade).
Yeah, part of his posts seems to suggest this, but then in the error output he has:

Code:
cat: /home/xxx/Downloads/digikam/digikam.SlackBuild: No such file or directory
Building directly from source wouldn't yield this message, I guess...

gargamel
 
Old 04-01-2013, 06:26 AM   #23
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,617

Rep: Reputation: 444Reputation: 444Reputation: 444Reputation: 444Reputation: 444
My only assumption during the process it was moved, deleted, or renamed by other process or he renamed it before the compilation start
 
Old 04-01-2013, 11:44 AM   #24
vdemuth
Member
 
Registered: Oct 2003
Location: West Midlands, UK
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
Posts: 770

Rep: Reputation: 94
Quote:
Originally Posted by ponce View Post
I think he builds and installs directly from source (and I'm wondering how he manages to remove old stuff when he needs to upgrade).
How wrong you are

Quote:
By any chance, did you rename the digikam.SlackBuild to another name?
Anyway, can't believe I made such a fundamental error, and managed to name the SlackBuild as Slackbuild without the capitalised B.

All up and running now.

Still stand by what I said about things really ought to be simpler in the 21st Century, but happy it's resolved.
 
Old 04-01-2013, 11:49 AM   #25
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,495

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Quote:
Originally Posted by vdemuth View Post
How wrong you are
sorry if I wasn't clear, I was responding to willysr following the post by Bazzaah.
 
Old 04-01-2013, 12:04 PM   #26
vdemuth
Member
 
Registered: Oct 2003
Location: West Midlands, UK
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
Posts: 770

Rep: Reputation: 94
Apologies for the mix up this end.
 
Old 04-01-2013, 12:06 PM   #27
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,495

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
no prob at all, I should have specified that I was referring to him (also gargamel thought I was referring to you)

Last edited by ponce; 04-01-2013 at 12:10 PM.
 
Old 04-01-2013, 02:01 PM   #28
Bazzaah
Member
 
Registered: Mar 2007
Distribution: Slackware64-current, Slackware64 14
Posts: 327

Original Poster
Rep: Reputation: 49
Quote:
Originally Posted by ponce View Post
I think he builds and installs directly from source (and I'm wondering how he manages to remove old stuff when he needs to upgrade).
Less than ideal but I tend just to delete the executable from /usr/bin - a messed up kind of reinstall. That said, the few programs I compile myself work very well and I don't get any error messages so it can't be that bad.

I should learn how to write a couple of SlackBuilds - that would be cleaner and make for easier maintenance.
 
Old 04-01-2013, 02:22 PM   #29
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,495

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Quote:
Originally Posted by Bazzaah View Post
Less than ideal but I tend just to delete the executable from /usr/bin - a messed up kind of reinstall. That said, the few programs I compile myself work very well and I don't get any error messages so it can't be that bad.
Let me say I wouldn't count on it at all
This way you will have old versions of stuff (libraries and whatever else get installed besides the binaries) laying around your filesystem and many strange and unexpected things can happen, not to say that it's very difficult to recover a clean installation from this situation.

If you prefer to have a clean system, use only slackbuild scripts to create packages and install those.
 
Old 04-01-2013, 03:05 PM   #30
Bazzaah
Member
 
Registered: Mar 2007
Distribution: Slackware64-current, Slackware64 14
Posts: 327

Original Poster
Rep: Reputation: 49
I take your points 100% but I only compile Digikam and Clementine so I'm not too worried, most (out of not many) installations I do through sbopkg.

What's the best SlackBuilds tut in your opinion?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Digikam from SBo does not compile on 64-current of 2010-03-09 gargamel Slackware 10 03-21-2010 06:28 PM
digikam no compile micder Slackware 2 02-13-2009 10:10 AM
digikam no compile micder Linux - Software 2 02-12-2009 10:06 AM
digikam install fails on dependecy ZaphyR Debian 4 03-10-2007 01:55 PM
digikam 0.6 compile error driving me MAD ! qwijibow Linux - Software 0 07-18-2004 02:06 PM


All times are GMT -5. The time now is 08:36 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration