libvpx: configure failure

[vgmbabbab@…]

I dont' know what the err message in log file says but it says it failed ;)

[cooljeanius (Eric Gallager)]

This is probably the relevant part of the log:

	:info:configure Unrecognized toolchain 'ppc32-darwin-gcc'

libvpx uses some x86 assembly in it so it makes sense that it would fail on ppc. This should probably be marked in the Portfile though.

[vgmbabbab@…]

Replying to egall@…:

This is probably the relevant part of the log:

	:info:configure Unrecognized toolchain 'ppc32-darwin-gcc'

libvpx uses some x86 assembly in it so it makes sense that it would fail on ppc. This should probably be marked in the Portfile though.

I'm actually trying to install gimp. and this was in deps list do i need libvpx to use gimp?

[larryv (Lawrence Velázquez)]

:debug:main Executing org.macports.main (libvpx)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.archivefetch (libvpx)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.fetch (libvpx)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.checksum (libvpx)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.extract (libvpx)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.patch (libvpx)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:configure configure phase started at Mon Feb 25 16:14:44 EST 2013
:notice:configure --->  Configuring libvpx

This was not a clean build attempt. Please run the following and attach the new main.log if it still fails.

sudo port clean libvpx && sudo port install libvpx

[neverpanic (Clemens Lang)]

This is a regression introduced by r100911. Jeremy, your commit message doesn't detail why this change was necessary. Do you want to fix this, or should I just revert your change?

[cooljeanius (Eric Gallager)]

Cc Me!

[jeremyhu (Jeremy Huddleston Sequoia)]

No need to revert it ... just do the same thing for ppc32 and ppc64 ... I'll do it

[jeremyhu (Jeremy Huddleston Sequoia)]

r103442

[cooljeanius (Eric Gallager)]

Replying to vgmbabbab@…:

Replying to egall@…:

This is probably the relevant part of the log:

	:info:configure Unrecognized toolchain 'ppc32-darwin-gcc'

libvpx uses some x86 assembly in it so it makes sense that it would fail on ppc. This should probably be marked in the Portfile though.

I'm actually trying to install gimp. and this was in deps list do i need libvpx to use gimp?

This is a little late, but libvpx is a video compression library used by ffmpeg, and ffmpeg is needed by gegl, which in turn is needed by gimp2. So it's 3 dependency levels down.

Edit: gegl actually lists ffmpeg as an optional dependency, not a needed one: ​http://www.gegl.org/#_dependencies

Perhaps the port for gegl could have its ffmpeg dependency moved to a variant? According to the link, libopenraw, libsdl, jpeg, openexr, and librsvg are also all optional dependencies; perhaps all of them could be moved to one big +optional_dependencies variant or something?

[ryandesign (Ryan Carsten Schmidt)]

Replying to egall@…:

Edit: gegl actually lists ffmpeg as an optional dependency, not a needed one: ​http://www.gegl.org/#_dependencies

Perhaps the port for gegl could have its ffmpeg dependency moved to a variant? According to the link, libopenraw, libsdl, jpeg, openexr, and librsvg are also all optional dependencies; perhaps all of them could be moved to one big +optional_dependencies variant or something?

Just because an upstream project considers some dependencies to be optional does not mean that we will necessarily make them optional in MacPorts.