hi to everyone,
since i now just started using slackware, i started installing just about everything from source tarballs and hunting down needed libraries. since this is kind of new to me i was wondering if someone can point me to a better understanding of things like:

-understanding the output and errors of make, make install
-how to find if i already have the libraries installed on my computer that the
software requires
-if and how libraries can conflict and how to audit/check for such instances
-what can happen when you try to overwrite old libraries and programs with new ones

sorry if this sounds kinda stupid, but i was used to binary packages and library dependency checking from other linux distributions. since i cant google my individual errors from my makefiles and end up with software i cant use, i need to understand this stuff better.

thanks much.

First of all, post the error messages here so we can assist you debug them.

or use pkgtool.

This usually pointed out in the library sources README, be sure to read them.

They most likely get overwritten. Most of the time things will work out fine but it could also cause serious issues depending on the library / file etc.

thank you. very helpful.

so i could just download the new firefox and install it right over the old one? slackware 12 comes with 2.0.0.4 as 2.0.0.5 is now current.
oh one more thing, how do you guys generally handle security updates on your software? on the slackware website there's a link to the latest security advisories, but i was wondering how the regular slackware user regularly updates?

I believe the regular Slackware user installs security updates by downloading the new package(s) (manually or by using rsync or some other method to keep up to date) and using upgradepkg, or by using a tool like slapt-get or swaret.

When you compile from source, if you don't specify the prefix configure option then by default the vast majority of programs install in /usr/local, so generally the software in /, /usr and /opt are safe from being overwritten (and by /usr I'm not including /usr/local, natch).

Personally I very rarely use "make install", preferring to create a package using checkinstall. You could also specify a prefix where you install each package and use makepkg. It will create a package you can use installpkg or upgradepkg with, and if you use checkinstall it will also create a "backup" package of everything that would be overwritten if you install the new package so you can use it to go back. to the way things were.

I'm not sure why you can't google individual errors from your attempted builds, unless you don't have internet access where the computer is... It's all a learning process, what better way to learn?

ok thanks.

uh...i was getting cryptic errors and warnings with a couple programs i was compiling that werent too friendly with the google search bar. haha.

just because i need to say this, i know jack s**t about linux in general, but im finding slackware easier to use than other distributions. it seems so much more simple and logical or something on those lines as things are coming together...if that makes any sense.