Changing kernel API / Breaking VirtualBox - update criteria violation?
sergio at serjux.com
Mon Dec 5 21:05:33 UTC 2011
On Mon, 2011-12-05 at 11:32 -0800, Josh Stone wrote:
> On 11/28/2011 12:47 PM, Chuck Ebbert wrote:
> > On Tue, 22 Nov 2011 10:06:32 -0800
> > Josh Stone <jistone at redhat.com> wrote:
> >> On 11/22/2011 09:51 AM, Michael Cronenworth wrote:
> >>> -#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 1, 0)
> >> It may have be helpful for the faked 2.6.4x kernels to still present a
> >> 3ish LINUX_VERSION_CODE. AFAIK, faking the number is for the benefit of
> >> userspace, not any kernel module. Perhaps it's not too late?
> > I've done this in the 22.214.171.124 update. Please try it.
> Sorry I didn't try sooner, as I don't actually have any pressing need
> for the change myself. But I happened to have the e1000e-1.6.3 source
> handy, which failed in kcompat.h on 126.96.36.199-1, but does compile
> successfully with 188.8.131.52-1. So, looks good to me!
Hi, Now I'm co-maintaining VirtualBox on rpmfusion
you got on my external link VB 4.1.4 for F15
if you try it let me know ,
in meantime I will read the begging of the thread, I also have some
doubts about the kernels 41.
But the main problem is, can't submit it on F15 because kBuild is not
updated (on F15) and I'm waiting for a decision on fesco about this
matter (update kBuild).
Sérgio M. B.
More information about the devel