How to update the available library list on Slackware

cstrieder · 09-17-2008, 11:57 PM

Let me explain what is going on:

I am using Slack 12.1 and I am trying to install a software A, but A depends on B. OK, no problem, that's common in Slackware. To solve this I first install software B and after install software A.

I am doing all of this in the Slask way, I want to say: ./configure, make and make install.

But the problem is, when a finished to install software B and come back trying to install software A again, it doesn't recognize that software B is installed and I need to reboot to update the available library list.

Some one knows a way of update this available library list, in a way that I don't need to reboot for this porpose?

Nylex · 09-18-2008, 12:45 AM

I believe running ldconfig is the way to do this.

Bruce Hill · 09-18-2008, 02:14 AM

Yes, and run "ldconfig" as root -- ref. "man ldconfig"

And btw -- the Slackware way is to make a Slackpackage
and use "installpkg"

cstrieder · 09-18-2008, 02:25 AM

Thanks guys,

yours reply was helpful.

But I recently discovered that the software B, that I was installing, wasn't on the $PATH and this is the problem. I have solved now.

Bruce Hill · 09-18-2008, 02:35 AM

I also thought of that. When you install with "./configure && make && make install",
iirc from my pre-SlackBuild script days, it installs to /usr/local rather than to the
Slackware path of /usr -- is that correct?

To make installing Slackware packages easier, with a SlackBuild script, you should try
Alien Bob's Alien's SlackBuild Toolkit.

cstrieder · 09-18-2008, 11:01 AM

hi bruce,

i think i don't understand your doubt exactly. my english is not so good.

are you asking, when i install any software if it installs to '/usr' or '/usr/local'?

Bruce Hill · 09-18-2008, 06:07 PM

When you install with "./configure && make && make install"
it installs the software to /usr/local.

And Slackware installs Slackware packages to /usr, so your
software installed with "./configure && make && make install"
is not found where Slackware packages are installed.

Therefore, the Slackware way is to create packages that install
themselves into "prefix=/usr". That way when you compile other
software later, that depends on it, things will install easier.
Meaning, you'll avoid the problem you had in this thread.

To make installing Slackware packages easier, with a SlackBuild script, you should try to use Alien Bob's Alien's SlackBuild Toolkit.

Here are some good Slackware links in Brazil.