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

[Sérgio Basto]

On Sex, 2012-09-14 at 19:05 +0200, Nicolas Chauvet wrote: 
> 2012/9/13 Sérgio M. Basto <sergiomb at rpmfusion.org>:
> > Author: sergiomb
> ...
> > +BuildRequires:  glibc(x86-32) glibc-devel(x86-32) libstdc++(x86-32)
> It should probably be enought with glibc-devel(x86-32) and
> libstdc++-devel(x86-32)

also doesn't work 
Error: No Package found for glibc(x86-32)
and
Error: No Package found for glibc-devel(x86-32) 

> 
> >  %changelog
> > +* Thu Sep 13 2012 Sérgio Basto <sergio at serjux.com> - 4.2.0-0.7.RC4
> > +- Another try to compile with 32-bits support on x86_64.
> 
> 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.

Best regards,
-- 
Sérgio M. B.