ffmpeg fails to build against ???

[LLLActive at GMX.Net]

On 29.01.13 19:38, Brandon Allbery wrote:
> On Tue, Jan 29, 2013 at 12:21 PM, LLLActive at GMX.Net <LLLActive at gmx.net 
> <mailto:LLLActive at gmx.net>> wrote:
>
>     Pardon, there was nolog file after the clean. It was the logfile
>     with the error build of ffmpeg. I can not get "sudo port upgrade
>     outdated" to run.
>
>
> Right, after the clean you have to try the build again; the point is 
> we need the log starting *from* a clean build, because if you just run 
> the build again without cleaning, it will skip past everything it 
> thinks succeeded.  We need to see a full, from the beginning, build log.
>
> As for port upgrade outdated, I guess what I said before made no sense 
> to you?  I'm not sure how to explain it... if there's nothing to 
> upgrade, it's not going to do anything except complain that there are 
> no outdated ports to upgrade.
>
Ok, I get it then that the following means all is OK, even if the 
"Error: No ports matched the given expression" is a little confusing. :-/

MM:~ MM$ sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.1.2 installed,
MacPorts base version 2.1.2 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you 
should run
   port upgrade outdated

MM:~ MM$ sudo port upgrade outdated
Error: No ports matched the given expression  = All OK then, nothing to 
upgrade then.

Thanks for the info.

:-)
Dreiel


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130129/d053dc27/attachment.html>