Bug 718933 - cannot build third-party modules based upon 2.6.33.9-rt31.66 packages
Summary: cannot build third-party modules based upon 2.6.33.9-rt31.66 packages
Keywords:
Status: CLOSED DUPLICATE of bug 718940
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel
Version: 2.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Red Hat Real Time Maintenance
QA Contact: David Sommerseth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-05 08:32 UTC by Robert Stonehouse
Modified: 2016-05-22 23:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-20 21:34:46 UTC
Target Upstream Version:


Attachments (Terms of Use)
include/generated from a full kernel build tree (20.41 KB, application/x-gzip)
2011-07-05 08:34 UTC, Robert Stonehouse
no flags Details

Description Robert Stonehouse 2011-07-05 08:32:15 UTC
Description of problem:
The compilation of a third party kernel module fails even with the correct kernel-rt-devel package installed.


Version-Release number of selected component (if applicable):
kernel-rt-2.6.33.9-rt31.66.el6rt.x86_64
kernel-rt-devel-2.6.33.9-rt31.66.el6rt.x86_64


How reproducible:
100%


Steps to Reproduce:
1. Compile any out of tree driver (simple example in bug 608784)
  

Actual results:
=============
    include/linux/mmzone.h:18:30: error: generated/bounds.h: No such file or
directory
    include/linux/mmzone.h:258:5: error: "MAX_NR_ZONES" is not defined
=============


Expected results:
Compile succeeds and module versioning in the generated .ko match the package kernel.


Additional info:
Related bug 608784 for MRG 1.2
Adding include/generated from a full kernel build tree allows the kernel module to compile and load.
I will attach a tgz

Comment 1 Robert Stonehouse 2011-07-05 08:34:43 UTC
Created attachment 511266 [details]
include/generated from a full kernel build tree

Comment 2 Clark Williams 2011-07-20 21:34:46 UTC

*** This bug has been marked as a duplicate of bug 718940 ***


Note You need to log in before you can comment on or make changes to this bug.