Bug 202416 - [sysutils/xvidcap] Shared object "libmp3lame.so.0" not found
Summary: [sysutils/xvidcap] Shared object "libmp3lame.so.0" not found
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Thierry Thomas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-18 13:46 UTC by Anton Shterenlikht
Modified: 2018-02-13 00:47 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (thierry)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Shterenlikht 2015-08-18 13:46:55 UTC 
installed via pkg:

# pkg info -xo xvidc
xvidcap-1.1.7_2,1              sysutils/xvidcap

rat> ldd /usr/local/bin/xvidcap |grep lame
        libmp3lame.so.0 => not found (0)
rat> xvidcap
Shared object "libmp3lame.so.0" not found, required by "xvidcap"
rat>
Comment 1 Thierry Thomas freebsd_committer freebsd_triage 2015-08-26 19:35:36 UTC 
I cannot reproduce this problem on my machines.

Could you please give more details? (uname -mr, date of your latest pkg upgrade, etc.)

Thanks.
Comment 2 Maxim Filimonov 2015-08-27 16:03:32 UTC 
Reproduced on my machine. FreeBSD 10.2-RELEASE-p2, amd64, the latest pkg upgrate dated today, 2015-08-27.

uname -mr says:
10.2-RELEASE amd64
Comment 3 Maxim Filimonov 2015-08-27 16:25:25 UTC 
Found out why it happens. For an unknown reason, audio/lame doesn't appear to be built for FreeBSD 10.2 amd64, so `pkg search ^lame` returns nothing. The solution was to install audio/lame from the ports tree. 
Then, another issue happened: 
Shared object "libx264.so.142" not found, required by "libavcodec.so.55"

The needed .so was definitely absent; instead, there was a newer one `libx264.so.144`, so I made a symlink from .so.144 to .so.142, and xvidcap launched just fine. 

The problem is: does it really only support .xwd output file format? Is there a way to make it support, you know, decent video formats?
Comment 4 Maxim Filimonov 2015-08-27 16:33:21 UTC 
What's even more strange is that audio/lame actually built just fine using poudriere on a 10.2-amd64 jail. You can find my poudriere log right there: https://build.bein.link/102amd64-default/2015-08-27_19h26m35s/logs/lame-3.99.5_2.log

I'm really sorry if I'm being annoying here. I'm just trying to provide as much debug info as you might need.
Comment 5 Thierry Thomas freebsd_committer freebsd_triage 2015-08-29 13:56:59 UTC 
(In reply to Maxim Filimonov from comment #4)
Thanks Maxim!
Never hesitate to add more details, every bit of info might be useful.
Comment 6 Thierry Thomas freebsd_committer freebsd_triage 2015-08-29 13:58:26 UTC 
Adding netchild (maintainer of lame) to Cc:
netchild, any idea about this problem?
Comment 7 Alexander Leidinger freebsd_committer freebsd_triage 2015-08-29 15:27:34 UTC 
(In reply to Thierry Thomas from comment #6)
Looks to me like something strange is going on on the portsbuild cluster or somewhere in the pkg distribution chain. As the LAME seems to be build (else the port couldn't have linked to the lame-lib), it doesn't look like a problem with LAME.
Comment 8 Walter Schwarzenfeld freebsd_triage 2018-01-12 07:56:36 UTC 
Is this still a problem? If not please close the PR.
Comment 9 Walter Schwarzenfeld freebsd_triage 2018-02-13 00:47:48 UTC 
xvidcap starts with recent version without error message. Seems solved.