FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 01-29-2010, 09:53 PM
Bernard
 
Default Ashamed was : serious problem upgrading sox

What a mess I have done with SoX !

I have solved my problem, at least the most urgent one, that is, getting
back to my older stable version of sox v14.0.1. The reason why it
behaved so strangely was that I had TWO sox in my system, the one I had
attempted to install from sources, and the one I had reinstalled from
the Lenny repository. A 'find / | grep sox' showed me that I had


a '/usr/bin/sox' file dated 25 may 2008, 31032 bytes long

and a

/usr/local/bin sox file dated 29 jan 2010, 117570 bytes long

I removed the newer file, and now, a call of 'sox' does work as it did
before I started fooling around.


Sorry for the trouble. I will later on make further attempts at
installing the newer version from testing/sid, as Tong recommends


Bernard wrote:

Bernard wrote:

Bernard wrote:

Boyd Stephen Smith Jr. wrote:


You'll have to get libsox0 installed before Lenny's sox will work.

I have just done this. The install went OK, so did the re-install of
Lenny's sox. But, when trying to call 'sox -h' (or any call to sox),
I get this :


bd@new-host:~$ sox -h
sox: error while loading shared libraries: libsox.so.1: cannot open
shared object file: No such file or directory

bd@new-host:~$

libsox.so.1 does not exist on my system, as
I was mistaking in writing that. True: apt-cache search did not show
any libsox.so.1 file, but I found one using 'find' :


/usr/local/lib/libsox.so.1 is there. Still any call to 'sox' sends
this same reply :


sox: error while loading shared libraries: libsox.so.1: cannot open
shared object file: No such file or directory



I just made another discovery. The 'man' file for sox that I presently
have on my system, is the one that belongs to sox v14.3, not the
manfile belonging to v14.0.1, where there was no mention of any -b
option. This knowledge reminds me that, prior to making an attempt to
install from 'testing' repositories, I had tried to install from a
source file that I had downloaded from sox.sourceforge.net. At first
sight, all had seemed to go allright, there was no error in 'make',
nor in 'make install', and some sox functions seemed to work, other
did not. This is when I decided to try the Debian way with testing ; I
thought that the new install would go over the old one. This
mismanagement may be part of the problem I now have.


But then, how shall I manually remove as much as possible of what
remains of that sox installed from source, as well as what remains of
the v14.3 installed from 'testing' ?






--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 01:40 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org