Sam Ravnborg wrote:
On Thu, Aug 04, 2005 at 11:57:55AM -0700, Roland Dreier wrote:
Sorry, I was too terse about the problem. You're right, but typical
distros don't ship full kernel source in their "support kernel builds"
package. And if I use an external build directory (ie "O=") then
the symlink just points to my external build directory, which doesn't
include the source to drivers/, just links to include/
If the external module uses a Kbuild file as explained in
Documentation/kbuild/makefiles.txt and then uses both O= and M=
when compiling the module there is no issue.
With respect to moving the .h files - please do so.
drivers/infiniband should only include header used in that same
directory. Not header files potentially uased by fs/.
I think Roland was talking about the case where the running kernel was
built with "O=", in which case the /lib/modules.../build symlink points
to the build directory rather than the original source tree.
Does Kbuild handle this case properly?
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |