libvpx: configure fails

[shazaum@…]

shazaum$ sudo port install opencv
Password:
Warning: port definitions are more than two weeks old, consider using selfupdate
--->  Computing dependencies for libvpx
--->  Configuring libvpx
Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
Log for libvpx is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/main.log
Error: Unable to upgrade port: 1
Error: Unable to execute port: upgrade ffmpeg failed
To report a bug, see <http://guide.macports.org/#project.tickets>

[shazaum@…]

Cc Me!

[shazaum@…]

correct version is 1.9.2

[neverpanic (Clemens Lang)]

Please remember to use WikiFormatting and set the port field as described in the Ticket Guidelines prominently linked from the "New Ticket" page. I have fixed the version field for you. You don't need to Cc yourself.

Is there a reason why you are running an outdated version of MacPorts and haven't synced your port tree in more than two weeks? Please consider running sudo port selfupdate (you might have to do this multiple times, it will tell you though) to update to the most recent release.

[ryandesign (Ryan Carsten Schmidt)]

Replying to cal@…:

Please remember to use WikiFormatting and set the port field as described in the Ticket Guidelines prominently linked from the "New Ticket" page. I have fixed the version field for you. You don't need to Cc yourself.

And please list the affected port in the Summary and Port fields.

Is there a reason why you are running an outdated version of MacPorts and haven't synced your port tree in more than two weeks? Please consider running sudo port selfupdate (you might have to do this multiple times, it will tell you though)

If you are running MacPorts earlier than 2.0.2, it will not tell you; if "sudo port selfupdate" updates you to a new version of MacPorts, you need to then run "sudo port selfupdate" a second time, even though it won't tell you to do so.

to update to the most recent release.

If, after selfupdating and running "sudo port clean libvpx" and trying again you still have a problem building libvpx, please attach the main.log here. Otherwise let us know it worked so that we can close this ticket.

[shazaum@…]

Replying to cal@…:

Please remember to use WikiFormatting and set the port field as described in the Ticket Guidelines prominently linked from the "New Ticket" page. I have fixed the version field for you. You don't need to Cc yourself.

ah, ok.. sorry

Is there a reason why you are running an outdated version of MacPorts and haven't synced your port tree in more than two weeks? Please consider running sudo port selfupdate (you might have to do this multiple times, it will tell you though) to update to the most recent release.

[shazaum@…]

Replying to ryandesign@…:

Replying to cal@…:

Please remember to use WikiFormatting and set the port field as described in the Ticket Guidelines prominently linked from the "New Ticket" page. I have fixed the version field for you. You don't need to Cc yourself.

And please list the affected port in the Summary and Port fields.

Is there a reason why you are running an outdated version of MacPorts and haven't synced your port tree in more than two weeks? Please consider running sudo port selfupdate (you might have to do this multiple times, it will tell you though)

If you are running MacPorts earlier than 2.0.2, it will not tell you; if "sudo port selfupdate" updates you to a new version of MacPorts, you need to then run "sudo port selfupdate" a second time, even though it won't tell you to do so.

to update to the most recent release.

If, after selfupdating and running "sudo port clean libvpx" and trying again you still have a problem building libvpx, please attach the main.log here. Otherwise let us know it worked so that we can close this ticket.

Clean in libvpx, fixed.. tks