rpms/VirtualBox/F-18 VirtualBox.spec, 1.17, 1.18 vboxweb.service, 1.1, 1.2

[Nicolas Chauvet]

2012/9/15 Sérgio Basto <sergio at serjux.com>:
> On Sex, 2012-09-14 at 19:05 +0200, Nicolas Chauvet wrote:
>> 2012/9/13 Sérgio M. Basto <sergiomb at rpmfusion.org>:
...
>> What does this 32bit support stands for ? Because usually we copy the
>> produced binary -libs sub-package from the "native" 32bit tree to the
>> x86_64 tree.
>> This is done automatically by the multilib script from the infra side.
>
> VirtualBox for x86_64 on configure test if have 32-bit support ,
> Checking for 32-bit support: OK. (on my mock build).
>
> and we patch the ./configure to not check that because it fails. I just
> want remove that patch and let VirtualBox configure him self without
> patching, seems to me better and closer to upstream, since it works on
> my mock builds.
If it's only a test, there is no need to worry, you can create a
disable 32bit test and submit it upstream.
But you seems to say that there are no 32bit binaries produced
elsewhere ? What this test is useful for ?

Nicolas (kwizart)