[vbox-dev] Svn Commit 48852 breaks build an Fedora17.x64 and Fedora18.x64

Peter Gsellmann pgsellmann at portner-elektronik.at
Thu Oct 10 11:46:25 UTC 2013

Hi Martin!

Am 2013-10-10 12:39, schrieb Martin Simmons:
>>>>>> On Thu, 10 Oct 2013 11:29:56 +0200, Peter Gsellmann said:
>> I have installed package  xz-libs,xz-devel  which contains  liblzma.so.5
>> but no  liblzma.a
>> From which package is the  liblzma.a  on your build machine?
>> Here,  yum provides /usr/lib64/liblzma.a  finds nothing.
> It looks like this is by design:
> https://bugzilla.redhat.com/show_bug.cgi?id=547011
What i see is the fedora people fight a cruisade against static
libraries (for whatever good reason) and at the same time VirtualBox
tries to use even more libraries in static format (for whatever good

Is this a conflict the VB-developers/maintainers should be aware of?

>From what i read in the linked document, fedoras remaining *-static
packages are 'threatened species'

Is VirtualBox supposed do be compilable on a Redhat/Fedora/CentOS machine?


More information about the vbox-dev mailing list