Why is it that ... ?
in [Slackware]
|
From: john on 1 Feb 2010 11:12 On Feb 1, 9:36 am, Mike Jones <N...(a)Arizona.Bay> wrote: > Responding to Robby Workman: > > [...] > > >> And why is it that when you compile a new package from source for > >> slackware it almost invariably fails? > > > It doesn't. This is called "projection" - the fact that it fails for > > *you* has zero bearing on the rest of the world. > > Confirmed. > > Of the various distros I've played with, Slack has the best "it worked" > ratio by far. On the odd occasion something can't find an expected lib or > other resource, I usually get all the info I need to know what it is I > need to do to fix that minor problem too. (Virtually all Slacker-created > slack.pkgs I've ever used "just work" too.) The major problems on Slack IME is the lack of libraries and auxiliaries called for by the packages. Getting these in place can be tedious. But currently my system sports: Open COBOL Tiny COBOL Inkscape (latest stable) Scribus (Latest unstable) Newer version of Gimp Recent version Open Office (etc.) The one sticking point is Quanta Plus. I don't want to run two versions of KDE, QT etc. on one partition. So I have a 12.1 partition just for Quanta. My current problem is getting either of the COBOL compilers to run on Win XP for testing cross compatiblity of user programs. John Culleton
From: Mike Jones on 1 Feb 2010 16:06 Responding to john(a)wexfordpress.com: > On Feb 1, 9:36 am, Mike Jones <N...(a)Arizona.Bay> wrote: >> Responding to Robby Workman: >> >> [...] >> >> >> And why is it that when you compile a new package from source for >> >> slackware it almost invariably fails? >> >> > It doesn't. This is called "projection" - the fact that it fails for >> > *you* has zero bearing on the rest of the world. >> >> Confirmed. >> >> Of the various distros I've played with, Slack has the best "it worked" >> ratio by far. On the odd occasion something can't find an expected lib >> or other resource, I usually get all the info I need to know what it is >> I need to do to fix that minor problem too. (Virtually all >> Slacker-created slack.pkgs I've ever used "just work" too.) > > The major problems on Slack IME is the lack of libraries and auxiliaries > called for by the packages. Getting these in place can be tedious. IM(ltd)E, this often depends on how you go about compiling things. For apps that need some vital extras, there are going to be times when Slackware doesn't have everything for everything already built in. Thats when the ambitious\huge\complex\specialist app's home pages should have guidence on what their apps need, even if its just electrolytes. ;) -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: John K. Herreshoff on 1 Feb 2010 16:41
Mike Jones wrote: > Responding to john(a)wexfordpress.com: > >> On Feb 1, 9:36�am, Mike Jones <N...(a)Arizona.Bay> wrote: >>> Responding to Robby Workman: >>> >>> [...] >>> >>> >> And why is it that when you compile a new package from source for >>> >> slackware it almost invariably fails? >>> >>> > It doesn't. �This is called "projection" - the fact that it fails for >>> > *you* has zero bearing on the rest of the world. >>> >>> Confirmed. >>> >>> Of the various distros I've played with, Slack has the best "it worked" >>> ratio by far. On the odd occasion something can't find an expected lib >>> or other resource, I usually get all the info I need to know what it is >>> I need to do to fix that minor problem too. (Virtually all >>> Slacker-created slack.pkgs I've ever used "just work" too.) >> >> The major problems on Slack IME is the lack of libraries and auxiliaries >> called for by the packages. Getting these in place can be tedious. > > > IM(ltd)E, this often depends on how you go about compiling things. > > For apps that need some vital extras, there are going to be times when > Slackware doesn't have everything for everything already built in. Thats > when the ambitious\huge\complex\specialist app's home pages should have > guidence on what their apps need, even if its just electrolytes. ;) > Ya know, when these apps are compiled, if a library is not found, the compiler chokes, and throws lots of errors telling you what is missing. True, you will probably have to google a bit to find what you need, but this method has always worked for me. if ./configure does not throw an error, then make -s will cook along until the problem shows up, and then I just do the make again, without -s, and I can get an idea what is missing. Often just searching for the error message will usually get me going again. YMMV. It helps to have some experience, but persistence will usually pay off. I built my first gimp from scratch about five years ago, and it took me a week to figure out what the compiler was trying to tell me. Then it got easier and easier. John. -- Using the Laptop at home. |