[vbox-dev] SVN requires libvpx-dev

Perry Halbert phalbert at cox.net
Sat May 25 21:20:05 GMT 2013


Oh I forgot to mention that I did edit the configure file to disable the 
WITH_LIBVPX but the switch should work, but doesn't.


On 05/25/2013 04:07 PM, Perry Halbert wrote:
> Hi Frank,
>
> Sorry to be so slow in responding but I just found time to revisit this.
> There still seems to be a problem.  Disabling libvpx using the 
> configure statement doesn't seem to be acceptable even though it is 
> stated as a valid switch.  RHEL/OEL 6 and Debian 6 don't have a new 
> enough version of libvpx to be able to build & the switch does not 
> allow me to proceed. It tells me that it is an unrecognized option.
>
>
> I snipped out all of the rest of the options to save space, but it 
> says that is the switch to use.
>
> /trunk$ ./configure --disable-libvpx
>
> Unrecognized option "--disable-libvpx"
>
> Usage: ./configure [OPTIONS]...
>
> Configuration:
> <snip>
>   --disable-libvpx         don't use libvpx for video capturing
> <snip>
>
>
> Perry
>
>
> On 05/06/2013 01:49 AM, Frank Mehnert wrote:
>> Hi Perry,
>>
>> On Saturday 04 May 2013 21:23:19 Perry Halbert wrote:
>>> I changed the testing logic in configure to allow version 0.9.0 and the
>>> build compiles without error and seems to function properly.  I guess
>>> the real question is will this come back to bite me in the seat of the
>>> pants or are the changes from 0.9.0 to 1.0.0 not one that will cause
>>> problems?  I really don't want to break the OEL-6.4 dependencies unless
>>> I simply must.
>>>
>>> __Copied from archive, using a different email client.__
>>>
>>> Seems to be checking for version libvpx* => 1.0.0
>>> Trying to install Version 1.0.0 warns about breaking dependencies on
>>> OEL6.4  Any idea how to make this build with version 0.9.0 or is this a
>>> lost cause until OEL upgrades?
>> at the moment, the VPX stuff is still disabled for public SVN builds.
>> I've disabled the VPX check in configure.
>>
>> We did not test VPX 0.9.0 yet so this version may indeed work. We will
>> verify if this version is sufficient.
>>
>> Kind regards,
>>
>> Frank
>>
>>
>> _______________________________________________
>> vbox-dev mailing list
>> vbox-dev at virtualbox.org
>> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>
>
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20130525/ac0d1745/attachment.html>


More information about the vbox-dev mailing list