[MacPorts] #25815: libvpx 0.9.1_0 fails to build

[MacPorts]

#25815: libvpx 0.9.1_0 fails to build
-------------------------------+--------------------------------------------
 Reporter:  manphiz@…          |       Owner:  raimue@…           
     Type:  defect             |      Status:  assigned           
 Priority:  Normal             |   Milestone:                     
Component:  ports              |     Version:  1.9.1              
 Keywords:                     |        Port:  libvpx             
-------------------------------+--------------------------------------------

Comment(by macports.20.cd@…):

 For those who may know how to edit a file in the terminal, but don't
 necessarily know all the arcana of how ports works, I'm going to add a bit
 more detail on how to do the workaround suggested by joerg at hydrops.han.de

 Joerg's workaround (hacking the sed line as seen above) worked for me. My
 error log was previously the same as the one shared by
 jwhowse4 at comcast.net.

 And eregontp at gmail.com also mentioned the steps in detail; I'm just going
 to make a bit more clear. This is on OS X; on other systems ymmv. Here are
 the steps:

 sudo port clean libvpx

 sudo port fetch libvpx

 sudo port extract libvpx

 cd to the staging directory where the port was being built - this
 directory should have been shown in one of the error messages. On my
 system it was
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/work/libvpx-0.9.1/

 then:

 cd build/make

 edit the configure.sh file in that folder to change the line as shown
 above.

 sudo port build libvpx
 sudo port install libvpx

 that worked for me.

 When you're done with this, if you are still in that staging directory,
 you'll find it has been removed out from under you. cd back to your home
 directory if you wanted to do anything else in the terminal (say, build
 another port that depeneded on libvpx), otherwise you'll get an error
 message.

 I don't know much about how ports work either. So I have empathy with my
 fellow macports newbies... thus the detail. Hopefully this is still
 helpful even after a patch has been added here.

 Maybe one of the experts can tell me if (and why) I should have used sudo
 port destroot libvpx instead of sudo port install libvpx at the end?

-- 
Ticket URL: <http://trac.macports.org/ticket/25815#comment:31>
MacPorts <http://www.macports.org/>
Ports system for Mac OS