Installing sources in the wrong directory.

stf92 · 05-11-2009, 07:41 PM

I installed a certain package, say foo.tar.
gz in this way: I untared foo.tar over directory .../juan/.
Then I compiled the sources:
.../juan> ./configue
.../juan> make
.../juan> make install
I saw no notification of a mistake at the end of any of each step issued on the console.
However, in /var/log/packages/., foo was no where to be
seen. And the case is that the programs ran well. Yet,
the main program was prgrm, and the installation left
a .../juan/.../prgrm.1. But 'man prgrm' got 'No manual
entry for prgrm'. Should I have untared over another directory? Is there a preferred dir for an installatio?
If it is so, please let me know. Regards.

i92guboj · 05-11-2009, 07:58 PM

Many things:

Quote:

Originally Posted by ENRIQUESTEFANINI

I installed a certain package, say foo.tar.
gz in this way: I untared foo.tar over directory .../juan/.
Then I compiled the sources:
.../juan> ./configue
.../juan> make
.../juan> make install

I am concerned about what user did you use to install this. The last step, "make install", writes to the root file system, which means that you usually will not be able to run it unless you are root, regulars users can't write on the system directories.

So, if you were operating as a user there must be an error, because users can't install software on system directories.

And if you were operating as root then you shouldn't do that. Only for the last step root is required, so the whole thing would be more like this:

Code:

$ ./configure
$ make
$ su -c 'make install'
<enter root password>

Quote:

However, in /var/log/packages/., foo was no where to be
seen.

I assume that /var/log/packages is where your distribution register the installed packages. Unfortunatelly, you didn't install a package, you compiled manually from source so you got to keep the pieces yourself. The system doesn't know anything about this software that you install by hand. If you want your distro to be aware of what you install, use the specific package manager for your distribution.

stf92 · 05-12-2009, 12:27 AM

You assume correctly. /var/log/packages is where my
distribution stores the packages and you have open my
eyes a bit. I installed as root (the three steps). I'll
follow your kind indications when I have to install soft-
ware in the future.

I'd like to enter into some detail. sox is an audio related program, whose manual says:
MP3 support in sox requires either or both EXTERNAL libmad and libmp3lame libraries. And these libraries were provided by foo.tar.gz during the instalation (in fact foo is nothing
else than a collection of libraries)
Does the word external mean that
that those libraries can be invisible to the system? For in this case, the source of malfunctioning must be somewhere else.

---------------------------------------------------------
Errata: 'And the case is that the programs ran well'.
Correction: the libraries didn't do their work, for when
running sox, sox output 'Sorry. No MP3 encoding support'.
--------------------------------------------------------

But enough of this. I presume you have more important things
to do than teaching newbies. Regards.

i92guboj · 05-12-2009, 12:45 AM

Quote:

Originally Posted by ENRIQUESTEFANINI

I'd like to enter into some detail. sox is an audio related program, whose manual says:
MP3 support in sox requires either or both EXTERNAL libmad and libmp3lame libraries.

I am not familiar with slackware to a big extent so I really don't know the state of things. But I am fairly familiar with sox, and it's a very common package that I think should be available in the form of an slackware package (forgive me if it isen't but it would be indeed very strange). Why are you wanting to compile it from source?

Using a standard package for your distro would solve all your problems, that is, unless you have a good reason to compile from source.

Quote:

But enough of this. I presume you have more important things
to do than teaching newbies. Regards.

Well, the forums are here to seek for help. If I weren't willing to give you a hand I wouldn't have "wasted" my time posting an answer in first place. So don't worry

brianL · 05-12-2009, 02:34 AM

Sox is already included in Slackware. Did you do a full install? If not, get the package off your CD/DVD or one of the mirrors. Always check if there's an official package available, or a SlackBuild, and if you need to compile anything from source use src2pkg.

http://slackbuilds.org/
http://distro.ibiblio.org/pub/linux/...nload/src2pkg/

stf92 · 05-13-2009, 12:51 AM

saludo]]]]]]]]

For two rea

stf92 · 05-13-2009, 01:20 AM

Yes. Slack comes with sox. Only that sox needs the libs. Unfortunately the libs are not in slack. So the need to compile (the libs). What I shall do is to uninstall the software in reverse order and reinstall. I hope this'll solve the problem. But, after all, it's only sound. Sorry for the delay.