LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Running before installing, from the source file directory. (https://www.linuxquestions.org/questions/slackware-14/running-before-installing-from-the-source-file-directory-861279/)

stf92 02-07-2011 07:13 PM
Running before installing, from the source file directory.
 
Kernel 2.6.21.5, GNU (Slackware 12.0).

Hi:
I compiled sox 14.3.1 (downloaded from sourceforge), which among its programs has sox and soxi. Before installing, and risking my old sox 12.18.1 installation I did what the INSTALL file says:
Quote:
Run
./sox file1.wav file1.ogg
, where ./sox is a wrap-around script, and it worked (that is, I ran in the source file directory). But the same thing, executed with soxi, ends in failure:
Code:
semoi@darkstar:~/prueba/sox-14.3.1/src$ ./soxi /home/semoi/ALSA/serkin.wav
/home/semoi/prueba/sox-14.3.1/src/.libs/lt-sox: SoX v14.3.1

/home/semoi/prueba/sox-14.3.1/src/.libs/lt-sox FAIL sox: Not enough input filenames specified

Usage summary: [gopts] [[fopts] infile]... [fopts] outfile [effect [effopt]]...

semoi@darkstar:~/prueba/sox-14.3.1/src$
But the man page is clear. It gives
Quote:
SYNOPSIS
soxi [-V[level]] [-T] [-t|-r|-c|-s|-d|-D|-b|-B|-e|-a] infile1 ...
as the syntax.

I do not want to through you a problem which is perhaps too specific, when I could get some help in the sox site, although I'm sure the problem has more to do with the specifics of a slackware installation and the parameters passed configure. So the question is more like how often are packages tested before installing and with what results. Regards.

Richard Cranium 02-07-2011 11:20 PM
If there is a difference between what the man page states and what the program itself tells you, I'd pick the latter.

andrew.46 02-08-2011 06:16 AM
Seems odd, my own setup is from -current:

Code:
andrew@skamandros~/music/ftgws$ sox --version
sox: SoX v14.3.1
andrew@skamandros~/music/ftgws$ soxi -V ftgws_06022011.ogg
soxi INFO formats: detected file format type `vorbis'

Input File    : 'ftgws_06022011.ogg'
Channels      : 2
Sample Rate    : 44100
Precision      : 16-bit
Duration      : 01:59:58.14 = 317437952 samples = 539860 CDDA sectors
File Size      : 129M
Bit Rate      : 143k
Sample Encoding: Vorbis
Comments      :
title=06-02-2011
artist=Stephen Watkins
album=For the God Who Sings

andrew@skamandros~/music/ftgws$
Does the -V option give any hints as to the failure? Also did you use PV's SlackBuild script to compile 14.3.1?

stf92 02-08-2011 09:18 AM
I did use -V with the same result. I downloaded the source package from sourceforge. PV's SlackBuild: I need a new tar program version to run the SB script. My tar does not understand the compressed file format. Do you know the name of the tar package for slack 13.1? Regards.

andrew.46 02-08-2011 03:11 PM
PV's SlackBuild can be easily modified to cope with the .tar.gz file that you have downloaded from SourceForge. Amongst other changes: Change build variable to 1, change numjobs variable to suit your machine, change final package to tgz.

stf92 02-08-2011 03:36 PM
I'll do what you say, or I'll try to, for it'll be a dificult job for me. But first: It is from version 7.1 that coreutils has .xz file capabilities. And mine is 6.9, the sources having been packed in a .xz format. So, I'm in the process of getting coreutils 7.1. Regards.

andrew.46 02-08-2011 03:50 PM
Hmmm..... you should not have to do this, simply download the source code for sox from SourceForge as you have done and then modify PV's Slackbuild as I have suggested. Something like the following:

http://www.andrews-corner.org/tmp/sox.SlackBuild

stf92 02-08-2011 04:31 PM
OK. Now see this:
Code:
semoi@darkstar:~/prueba/sb_sox-14.3.1$ ls -l
total 712
-rw-r--r-- 1 semoi users    710 2011-02-08 10:48 slack-desc
-rw-r--r-- 1 semoi users 711816 2011-02-08 10:48 sox-14.3.1.tar.xz
-rw-r--r-- 1 semoi users  3452 2011-02-08 10:50 sox.SlackBuild
-rwxr-xr-x 1 semoi users  3648 2011-02-08 19:14 sox.SlackBuild_modified*
semoi@darkstar:~/prueba/sb_sox-14.3.1$ sudo ./sox.SlackBuild_modified
tar: /home/semoi/prueba/sb_sox-14.3.1/sox-14.3.1.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
What do you think?

andrew.46 02-08-2011 04:49 PM
Indeed, because I altered the SlackBuild to cater for your original download from SourceForge, which of course is sox-14.3.1.tar.gz :). This can be (re-)downloaded as:

Code:
wget 'http://transact.dl.sourceforge.net/project/sox/sox/14.3.1/sox-14.3.1.tar.gz'

stf92 02-08-2011 05:43 PM
My mistake, I apologize. I'm compiling, waiting to see what the resulting binaries will do when I type 'soxi some_file.wav'. Soxi will be a copy or a link to sox, but it must admit only one argument if I want. And it'll do an entirely different thing than the sox command. When I get the first results I'll let the forum know.

stf92 02-08-2011 06:20 PM
No use. Dependencies are a big problem in sox.
 
Hi:

Well. Compilation went all right. I use explodepkg (not installpkg) to test the sox binary file in a separate directory.
I launched it and, alas, it complains about the libsox.so.1 shared library lacking. And it certainly does lack. In all of my disk, including the recently exploded package.

Of course I can download libsox.so.1 too. But only to find, sure, I must keep downloading other libraries. Please consider I run Slackware 12.0 and sox-14.3.1 is from Slackware 13.x. Isn't it time to give up? Regards.

andrew.46 02-08-2011 06:31 PM
I would suggest using upgradepkg to install the new sox pkg, if there are problems remove it with removepkg and reinstall the old sox package from your installation CD/DVD.

T3slider 02-08-2011 07:29 PM
Quote:
Originally Posted by stf92 (Post 4252461)
Hi:

Well. Compilation went all right. I use explodepkg (not installpkg) to test the sox binary file in a separate directory.
I launched it and, alas, it complains about the libsox.so.1 shared library lacking. And it certainly does lack. In all of my disk, including the recently exploded package.

Of course I can download libsox.so.1 too. But only to find, sure, I must keep downloading other libraries. Please consider I run Slackware 12.0 and sox-14.3.1 is from Slackware 13.x. Isn't it time to give up? Regards.
From doinst.sh:
Code:
( cd usr/lib ; rm -rf libsox.so.1 )
( cd usr/lib ; ln -sf libsox.so.1.0.0 libsox.so.1 )
If you installed the package it would work (unless there is another error to come...). Otherwise you can create the link within the exploded package directories and export LD_LIBRARY_PATH or something to that effect.

stf92 02-08-2011 10:03 PM
i would have liked to use T3slider's approach (I had already look ed into doinst.sh and had made a removed and made a link, don't remember well; the next logical step was to relink those libraries) but the LD_LIBRARY_PATH thing made a coward of me.

So, at last, I decided to follow Andrew's advice and install. Result: success. Watching the screen, by the way, as upgradepkg was running, I saw both versions use the same libraries, for not a single one was removed. And no new one was added.

A note: the new binary package was the output of the SlackBuilds script as modified by Andrew. To him, as well as to the other LQers, kind regards.


All times are GMT -5. The time now is 07:22 PM.