| Summary: | Can't build multimedia/ffmpeg & multimedia/ffmpeg0 ; missing doc files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | fossette <dodo1> | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Only Me | CC: | multimedia, portmaster, wg | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | amd64 | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
fossette
2015-10-06 02:12:24 UTC
After reading about similar problems with other ports on the FreeBSD Forums, I checked my system for the same pattern, and got the problem solved. So, I'll switch this bug report state to closed, but I have no idea how it came about, nor how to reproduce it. In a similar problem post, one user mentioned having encountered a similar problem when perl wasn't up to date. But as listed in my portmaster list, my version of perl is right. Another user asked for some installation log file (sorry, I don't recall the name). The one I found had a line saying the /usr/local/bin/perl was missing. Wtf? To fix this mess, I ran (in the /usr/ports/lang/perl5.20/ directory): # portsnap fetch update (just to be sure) # make deinstall # make install clean I was then able to built the other ports successfully, multimedia/ffmpeg etc... (In reply to fossette from comment #1) > > In a similar problem post, one user mentioned having encountered a similar > problem when perl wasn't up to date. But as listed in my portmaster list, > my version of perl is right. Another user asked for some installation log > file (sorry, I don't recall the name). The one I found had a line saying > the /usr/local/bin/perl was missing. Wtf? > > To fix this mess, I ran (in the /usr/ports/lang/perl5.20/ directory): > # portsnap fetch update (just to be sure) > # make deinstall > # make install clean Yes. That's because the current state of Perl [on FreeBSD] is a bit of a disaster. I believe there is some mention of it in UPDATING. But it is not yet completely cleaned up/cured. |