From: "Art Vandelay" <artvandelay@tbns.org>
To: <backports@vger.kernel.org>
Subject: Compiling backports-3.14.22-1 against kernel v2.6.32
Date: Wed, 5 Nov 2014 20:44:55 -0800 [thread overview]
Message-ID: <20141105204455.80F94044@m0048140.ppops.net> (raw)
Hi Everyone,
I'm currently running RHEL6 since it's still the latest stable release and can't upgrade to RHEL7. And the latest kernel version available for RHEL6 is v2.6.32.
So when I tried to build the driver for RTL8723AE from backports-3.14.22-1 (because the front page says to use 3.14 for kernel versions 2.6.26+), I got these compilation errors:
backports-3.14.22-1/backport-include/net/inet_frag.h: In function 'backport_frag_mem_limit':
backports-3.14.22-1/backport-include/net/inet_frag.h:11: error: 'struct netns_frags' has no member named 'mem'
backports-3.14.22-1/backport-include/net/inet_frag.h: In function 'backport_sub_frag_mem_limit':
backports-3.14.22-1/backport-include/net/inet_frag.h:17: error: 'struct netns_frags' has no member named 'mem'
backports-3.14.22-1/backport-include/net/inet_frag.h: In function 'backport_add_frag_mem_limit':
backports-3.14.22-1/backport-include/net/inet_frag.h:23: error: 'struct netns_frags' has no member named 'mem'
backports-3.14.22-1/backport-include/net/inet_frag.h: In function 'backport_init_frag_mem_limit':
backports-3.14.22-1/backport-include/net/inet_frag.h:29: error: 'struct netns_frags' has no member named 'mem'
backports-3.14.22-1/backport-include/net/inet_frag.h: In function 'backport_sum_frag_mem_limit':
backports-3.14.22-1/backport-include/net/inet_frag.h:35: error: 'struct netns_frags' has no member named 'mem'
make[6]: *** [backports-3.14.22-1/compat/compat-2.6.35.o] Error 1
make[5]: *** [backports-3.14.22-1/compat] Error 2
make[4]: *** [_module_backports-3.14.22-1] Error 2
I understand that only kernel versions >= 3.0 are being supported at the moment, but backports-3.14 was supposed to successfully build against kernel-2.6.32 and it doesn't in my case. Anyway, it doesn't seem like it would be a difficult fix; any help would be appreciated.
Thanks!
_____________________________________________________________
Brought to you by TBNS.net
reply other threads:[~2014-11-06 4:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141105204455.80F94044@m0048140.ppops.net \
--to=artvandelay@tbns.org \
--cc=backports@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox