Woosh
hi guys just wonted to show how happy i was to get woosh to work with the network manager in ubuntu 8.10. just put my password and user dealy in the "dsl" connections didn't work right away but after reboot it connected i was very surprised it was ten times easier than i thought it would be. Its not bad definitely slower than telestra in chch but i'm invercragill so i couldn't get telestra
Re: Dynamically loadable library woes
On Tue, Feb 24, 2009 at 4:45 PM, Stephen Irons wrote: > Christopher Sawtell wrote: >> >> On Tuesday 24 February 2009 12:37:45 Stephen Irons wrote: >> > I have installed ffmpeg from the Ubuntu repositories. >> >> >> man gcc >> >> >> pay particular attention to the -L option flag. >> >> >> and then if you are an obedient purist, alter the necessary configuration >> files, generate a new .deb file and install form that. >> >> >> Being an obedient purist is seriously recommended. >> >> >> -- >> With Sincerity, >> Christopher Sawtell > > -L/usr/local/bin as an option to gcc did not change anything. I think that > option only affects static linking -- it tells the linker where to look for > libraries. Or perhaps where to find the stubs necessary to link a library > dynamically. But it did not affect the loading at run-time. > > But I found two solutions: > > 1. ./configure --extra-ldflags=-Wl,-rpath/usr/local/bin stores that path in > the executable to tell the program loader to also search /usr/local/bin for > libraries. > > 2. ./configure --build-suffix=-ZZZ changes the names of the libraries to > lib-avcodec-ZZZ.so.66.whatever. These names are stored in the executable, so > they are found correctly. > > man ld gives the full search order for *linking*: > > * -rpath-link options > * -rpath options > * LD_RUN_PATH environment variable > * On *SunOS*, directories specified using -L -- this is what > Christopher Sawtell suggested, but does not work on Linux > * LD_LIBRARY_PATH > * DT_RUNPATH or DT_RPATH > * default directories /lib and /usr/lib > * directories in /etc/ld.so.conf > > man ld.so gives a different order for *loading*: > > * LD_LIBRARY_PATH > * From the cache file /etc/ld.so.cache, created by ldconfig > * /lib and /usr/lib > > But this does not describe what I actually saw happening, so I prefer the > search order given in man ld. I think that the *linker* was finding the > necessary library stubs in /usr/lib, so it never bothered to look in > /usr/local/lib. > > Anyway, my version of ffmpeg with AMR support is now working...so I can once > again convert videos from my phone to ... whatever ... they are still > rubbish. > > I should probably make a .deb package so that I can install into /usr/bin > and /usr/lib so that other applications get the newer version of ffmpeg and > libav* ... but what will it break? Nothing, provided that the library > authors have got their version numbering correct. > > Stephen Irons perhaps it would be easier to use the medibuntu repos. My ff,eg from medibuntu boasts: --enable-amr_nb --enable-amr_wb would that do the trick?
Re: Dynamically loadable library woes
You'll probably find you're missing the 64 bit version ( or the 32 bit version ) of the library... Steve On Tue, 24 Feb 2009 16:45:05 +1300 Stephen Irons wrote: > Christopher Sawtell wrote: > > On Tuesday 24 February 2009 12:37:45 Stephen Irons wrote: > > > I have installed ffmpeg from the Ubuntu repositories. > > > > > > man gcc > > > > > > pay particular attention to the -L option flag. > > > > > > and then if you are an obedient purist, alter the necessary > > configuration files, generate a new .deb file and install form that. > > > > > > Being an obedient purist is seriously recommended. > > > > > > -- > > With Sincerity, > > Christopher Sawtell > > -L/usr/local/bin as an option to gcc did not change anything. I think > that option only affects static linking -- it tells the linker where to > look for libraries. Or perhaps where to find the stubs necessary to link > a library dynamically. But it did not affect the loading at run-time. > > But I found two solutions: > > 1. ./configure --extra-ldflags=-Wl,-rpath/usr/local/bin stores that path > in the executable to tell the program loader to also search > /usr/local/bin for libraries. > > 2. ./configure --build-suffix=-ZZZ changes the names of the libraries to > lib-avcodec-ZZZ.so.66.whatever. These names are stored in the > executable, so they are found correctly. > > man ld gives the full search order for *linking*: > > * -rpath-link options > * -rpath options > * LD_RUN_PATH environment variable > * On *SunOS*, directories specified using -L -- this is what > Christopher Sawtell suggested, but does not work on Linux > * LD_LIBRARY_PATH > * DT_RUNPATH or DT_RPATH > * default directories /lib and /usr/lib > * directories in /etc/ld.so.conf > > man ld.so gives a different order for *loading*: > > * LD_LIBRARY_PATH > * From the cache file /etc/ld.so.cache, created by ldconfig > * /lib and /usr/lib > > But this does not describe what I actually saw happening, so I prefer > the search order given in man ld. I think that the *linker* was finding > the necessary library stubs in /usr/lib, so it never bothered to look in > /usr/local/lib. > > Anyway, my version of ffmpeg with AMR support is now working...so I can > once again convert videos from my phone to ... whatever ... they are > still rubbish. > > I should probably make a .deb package so that I can install into > /usr/bin and /usr/lib so that other applications get the newer version > of ffmpeg and libav* ... but what will it break? Nothing, provided that > the library authors have got their version numbering correct. > > Stephen Irons > > === > This email, including any attachments, is only for the intended > addressee. It is subject to copyright, is confidential and may be > the subject of legal or other privilege, none of which is waived or > lost by reason of this transmission. > If the receiver is not the intended addressee, please accept our > apologies, notify us by return, delete all copies and perform no > other act on the email. > Unfortunately, we cannot warrant that the email has not been > altered or corrupted during transmission. > === > -- Steve Holdoway
Re: Dynamically loadable library woes
Christopher Sawtell wrote: On Tuesday 24 February 2009 12:37:45 Stephen Irons wrote: > I have installed ffmpeg from the Ubuntu repositories. man gcc pay particular attention to the -L option flag. and then if you are an obedient purist, alter the necessary configuration files, generate a new .deb file and install form that. Being an obedient purist is seriously recommended. -- With Sincerity, Christopher Sawtell -L/usr/local/bin as an option to gcc did not change anything. I think that option only affects static linking -- it tells the linker where to look for libraries. Or perhaps where to find the stubs necessary to link a library dynamically. But it did not affect the loading at run-time. But I found two solutions: 1. ./configure --extra-ldflags=-Wl,-rpath/usr/local/bin stores that path in the executable to tell the program loader to also search /usr/local/bin for libraries. 2. ./configure --build-suffix=-ZZZ changes the names of the libraries to lib-avcodec-ZZZ.so.66.whatever. These names are stored in the executable, so they are found correctly. man ld gives the full search order for *linking*: * -rpath-link options * -rpath options * LD_RUN_PATH environment variable * On *SunOS*, directories specified using -L -- this is what Christopher Sawtell suggested, but does not work on Linux * LD_LIBRARY_PATH * DT_RUNPATH or DT_RPATH * default directories /lib and /usr/lib * directories in /etc/ld.so.conf man ld.so gives a different order for *loading*: * LD_LIBRARY_PATH * From the cache file /etc/ld.so.cache, created by ldconfig * /lib and /usr/lib But this does not describe what I actually saw happening, so I prefer the search order given in man ld. I think that the *linker* was finding the necessary library stubs in /usr/lib, so it never bothered to look in /usr/local/lib. Anyway, my version of ffmpeg with AMR support is now working...so I can once again convert videos from my phone to ... whatever ... they are still rubbish. I should probably make a .deb package so that I can install into /usr/bin and /usr/lib so that other applications get the newer version of ffmpeg and libav* ... but what will it break? Nothing, provided that the library authors have got their version numbering correct. Stephen Irons === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. ===
Re: Hardy 8.04 modem concerns
That's an external one, isn't it?? So can you talk to it on /dev/ttyS0 or is it on ttyS1? ( try connecting to it with minicom, and typing ATZ - it'll answer OK if it is, then you'll be sure which device it's on ). Other options, like is it waiting for a dialtone ( maybe from the wrong country? ) before dialling, or can you connect to the clear account that you know the modem can connect to on other machines?? Hopefully that'll help to identify which bit is playing up... Steve On Tue, 24 Feb 2009 16:27:26 +1300 chris wrote: > Hi Steve, > Can we start again please? > the modem is a diamond 56e supra express pro. > I use it successfully on my other two machines where it connects > flawlessly to clear. > However on this machine it will not pass on to Xtra and times out after > 24 seconds. > > Attached is the output from lspic > > will be grateful for any help you can give > Regards Chris Thomas > > On Tue, 2009-02-24 at 15:41 +1300, Steve Holdoway wrote: > > On Tue, 24 Feb 2009 15:33:20 +1300 > > chris wrote: > > > > > Hi All > > > I can not connect from my hardy partition to xtra, using either wvdial, > > > or gnome pp. > > > This same machine will connect using the the same modem from the windows > > > partition. > > > Can anyone please offer any sugestions? > > > > > > Regards Chris Thomas > > > > > Hi Chris, > > > > Knowing what the modem was ( sudo lspci should tell you ) will make support > > easier (: > > > > Cheers, Steve > -- Steve Holdoway
Re: Hardy 8.04 modem concerns
Err, of course, if it's a dual-boot PC and it was *just working* with the other OS then of course the first three reasons I suggest are moot. A On Tue, February 24, 2009 16:39, Andrew Errington wrote: > Well, it seems to be an external serial modem, so it ought to work. > > > Common problems are: > > > Modem not switched on > Modem not connected to PC > Modem not connected to phone line > Misidentifying the serial port (/dev/ttyS?) > Permissions on the serial port device > Mis-typing the ISP phone number, username, or password > > > These are the easy ones to detect and fix. > > > By the way, I used KPPP for modem trickery and it seemed to do the Right > Thing (but no good if you use Gnome). > > > HTH, > > > Andrew > > > > >
RE: Hardy 8.04 modem concerns
You say it times out, do you get a ppp log of the session? -Original Message- From: chris [mailto:che...@gmail.com] Sent: Tuesday, 24 February 2009 4:31 pm To: linux-users@it.canterbury.ac.nz Subject: Re: Hardy 8.04 modem concerns sorry Steve the information I sent you was from the wrong machine :-( I have just resent the correct info Regards Chris On Tue, 2009-02-24 at 16:25 +1300, Steve Holdoway wrote: > Looks like you may need to trawl through the intel website for the right drivers ): > > Cheers, > > Steve. > > On Tue, 24 Feb 2009 16:07:39 +1300 > chris wrote: > > > Forgot, modem is attached to ttyso > > Cheers Chris > > not ttyusb0 > > I am having to send this from another machine not the one that won't > > connect. > > > > On Tue, 2009-02-24 at 15:41 +1300, Steve Holdoway wrote: > > > On Tue, 24 Feb 2009 15:33:20 +1300 chris wrote: > > > > > > > Hi All > > > > I can not connect from my hardy partition to xtra, using either > > > > wvdial, or gnome pp. > > > > This same machine will connect using the the same modem from the > > > > windows partition. > > > > Can anyone please offer any sugestions? > > > > > > > > Regards Chris Thomas > > > > > > > Hi Chris, > > > > > > Knowing what the modem was ( sudo lspci should tell you ) will make support easier (: > > > > > > Cheers, Steve > > > > ** This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Christchurch City Council. If you are not the correct recipient of this email please advise the sender and delete. Christchurch City Council http://www.ccc.govt.nz **
Re: Hardy 8.04 modem concerns
Well, it seems to be an external serial modem, so it ought to work. Common problems are: Modem not switched on Modem not connected to PC Modem not connected to phone line Misidentifying the serial port (/dev/ttyS?) Permissions on the serial port device Mis-typing the ISP phone number, username, or password These are the easy ones to detect and fix. By the way, I used KPPP for modem trickery and it seemed to do the Right Thing (but no good if you use Gnome). HTH, Andrew
Re: Hardy 8.04 modem concerns
sorry Steve the information I sent you was from the wrong machine :-( I have just resent the correct info Regards Chris On Tue, 2009-02-24 at 16:25 +1300, Steve Holdoway wrote: > Looks like you may need to trawl through the intel website for the right > drivers ): > > Cheers, > > Steve. > > On Tue, 24 Feb 2009 16:07:39 +1300 > chris wrote: > > > Forgot, modem is attached to ttyso > > Cheers Chris > > not ttyusb0 > > I am having to send this from another machine not the one that won't > > connect. > > > > On Tue, 2009-02-24 at 15:41 +1300, Steve Holdoway wrote: > > > On Tue, 24 Feb 2009 15:33:20 +1300 > > > chris wrote: > > > > > > > Hi All > > > > I can not connect from my hardy partition to xtra, using either wvdial, > > > > or gnome pp. > > > > This same machine will connect using the the same modem from the windows > > > > partition. > > > > Can anyone please offer any sugestions? > > > > > > > > Regards Chris Thomas > > > > > > > Hi Chris, > > > > > > Knowing what the modem was ( sudo lspci should tell you ) will make > > > support easier (: > > > > > > Cheers, Steve > > > >
Re: Hardy 8.04 modem concerns
Hi Steve, Can we start again please? the modem is a diamond 56e supra express pro. I use it successfully on my other two machines where it connects flawlessly to clear. However on this machine it will not pass on to Xtra and times out after 24 seconds. Attached is the output from lspic will be grateful for any help you can give Regards Chris Thomas On Tue, 2009-02-24 at 15:41 +1300, Steve Holdoway wrote: > On Tue, 24 Feb 2009 15:33:20 +1300 > chris wrote: > > > Hi All > > I can not connect from my hardy partition to xtra, using either wvdial, > > or gnome pp. > > This same machine will connect using the the same modem from the windows > > partition. > > Can anyone please offer any sugestions? > > > > Regards Chris Thomas > > > Hi Chris, > > Knowing what the modem was ( sudo lspci should tell you ) will make support > easier (: > > Cheers, Steve ve...@verna-desktop:~$ sudo lspci [sudo] password for verna: 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03) 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82) 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02) 01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Controller (rev 82)
Re: Hardy 8.04 modem concerns
Looks like you may need to trawl through the intel website for the right drivers ): Cheers, Steve. On Tue, 24 Feb 2009 16:07:39 +1300 chris wrote: > Forgot, modem is attached to ttyso > Cheers Chris > not ttyusb0 > I am having to send this from another machine not the one that won't > connect. > > On Tue, 2009-02-24 at 15:41 +1300, Steve Holdoway wrote: > > On Tue, 24 Feb 2009 15:33:20 +1300 > > chris wrote: > > > > > Hi All > > > I can not connect from my hardy partition to xtra, using either wvdial, > > > or gnome pp. > > > This same machine will connect using the the same modem from the windows > > > partition. > > > Can anyone please offer any sugestions? > > > > > > Regards Chris Thomas > > > > > Hi Chris, > > > > Knowing what the modem was ( sudo lspci should tell you ) will make support > > easier (: > > > > Cheers, Steve > -- Steve Holdoway
Re: Hardy 8.04 modem concerns
Forgot, modem is attached to ttyso Cheers Chris not ttyusb0 I am having to send this from another machine not the one that won't connect. On Tue, 2009-02-24 at 15:41 +1300, Steve Holdoway wrote: > On Tue, 24 Feb 2009 15:33:20 +1300 > chris wrote: > > > Hi All > > I can not connect from my hardy partition to xtra, using either wvdial, > > or gnome pp. > > This same machine will connect using the the same modem from the windows > > partition. > > Can anyone please offer any sugestions? > > > > Regards Chris Thomas > > > Hi Chris, > > Knowing what the modem was ( sudo lspci should tell you ) will make support > easier (: > > Cheers, Steve
Re: Hardy 8.04 modem concerns
Hi Steve, Diamond supra express 65e proch...@chris-laptop:~$ sudo lspci [sudo] password for chris: 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07) 00:03.2 IDE interface: Intel Corporation Mobile 4 Series Chipset PT IDER Controller (rev 07) 00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection (rev 07) 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation Device 061e (rev a2) 03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100 86:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 06) 86:06.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 25) 86:06.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 14) 86:06.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 14) 86:06.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 14) 86:06.5 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev bb) output from sudo lspci below On Tue, 2009-02-24 at 15:41 +1300, Steve Holdoway wrote: > On Tue, 24 Feb 2009 15:33:20 +1300 > chris wrote: > > > Hi All > > I can not connect from my hardy partition to xtra, using either wvdial, > > or gnome pp. > > This same machine will connect using the the same modem from the windows > > partition. > > Can anyone please offer any sugestions? > > > > Regards Chris Thomas > > > Hi Chris, > > Knowing what the modem was ( sudo lspci should tell you ) will make support > easier (: > > Cheers, Steve
Re: Hardy 8.04 modem concerns
On Tue, 24 Feb 2009 15:33:20 +1300 chris wrote: > Hi All > I can not connect from my hardy partition to xtra, using either wvdial, > or gnome pp. > This same machine will connect using the the same modem from the windows > partition. > Can anyone please offer any sugestions? > > Regards Chris Thomas > Hi Chris, Knowing what the modem was ( sudo lspci should tell you ) will make support easier (: Cheers, Steve -- Steve Holdoway
Hardy 8.04 modem concerns
Hi All I can not connect from my hardy partition to xtra, using either wvdial, or gnome pp. This same machine will connect using the the same modem from the windows partition. Can anyone please offer any sugestions? Regards Chris Thomas
Re: Dynamically loadable library woes
On Tuesday 24 February 2009 12:37:45 Stephen Irons wrote: > I have installed ffmpeg from the Ubuntu repositories. man gcc pay particular attention to the -L option flag. and then if you are an obedient purist, alter the necessary configuration files, generate a new .deb file and install form that. Being an obedient purist is seriously recommended. -- With Sincerity, Christopher Sawtell
Dynamically loadable library woes
I have installed ffmpeg from the Ubuntu repositories. This creates the following files: * /usr/bin/ffmpeg * /usr/lib/libavcodec.so.51.50 * /usr/lib/libavformat.so.52.7.0 * /usr/lib/i686/cmov/libavcodec.so.51 * /usr/lib/i686/cmov/libavformat.so.52 as well as some others, including some symlinks. I have also built a new version of ffmpeg from the ffmpeg project. This creates the following files: * /usr/local/bin/ffmpeg * /usr/local/lib/libavcodec.so.52.18 * /usr/local/lib/libavformat.so.52.29.2 and some others. $ which ffmpeg reports /usr/local/bin. When I run ffmpeg, it fails with a message about a missing symbol. I know that all the libraries have been built correctly, because if I set LD_LIBRARY_PATH=/usr/local/lib, then my new ffmpeg works correctly. I read somewhere on google that it is Bad to set LD_LIBRARY_PATH, except during development or to work around problems that have no other solution. I have modified /etc/ld.so.conf, adding /usr/local/lib at the top of the file, and run ldconfig -v; it indicates that the correctly libraries are there in /usr/local/lib, and are at the top of the listing, so I assume that they are loaded first. Now, the only indication that something is wrong comes from $ ldd /usr/local/bin/ffmpeg : : snip : libavformat.so.52 => /usr/lib/i686/cmov/libavformat.so.52 (0xb7ffa000) libavcodec.so.52 => /usr/local/lib/libavcodec.so.52 (0xb7823000) This shows that /usr/local/bin/ffmpeg is trying to use version 52 of libavcodec; there is only the one in /usr/local/lib, so it uses the right one. However, it is trying to use version 0.52 of libavformat: there are two of these. For some reason, it is ignoring the setting in /etc/ld.so.conf and using the /usr/lib/i686/... version instead of my one. * Is there something INSIDE /usr/local/bin/ffmpeg that makes it prefer the /usr/lib... version? If so, how do I override it? * Is /etc/ld.so.conf and ldconfig broken? * ./configure can somehow detect which libraries are installed. Perhaps this is broken and uses the wrong search path. * How do I make it use MY version of libavcodec, libavformat, etc without resorting to LD_LIBRARY_PATH? * There is another library (libx264) that gives the same problem... Some heavyweight solutions spring to mind: * install into /usr/bin and /usr/lib, overwriting those files from the packages; however, I am concerned that this will break during upgrades. * remove ffmpeg and its dependencies; however, this will mean uninstalling everything that depends on these packages. I would prefer not to do this. * create my own .deb package and install that === This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. ===
