Summary: | net-fs/davfs2-0.2.2 does not compile because of kernel headers | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tklauser |
Component: | Current packages | Assignee: | Stefan Schweizer (RETIRED) <genstef> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2004.2 | ||
Hardware: | x86 | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Makefile.in patch to fix the path to kernel headers
New ebuild for davfs-0.2.2 Ebuild with correct header Patch to make davfs build against 2.6 |
Description
tklauser
2004-09-01 05:26:06 UTC
Created attachment 38670 [details, diff]
Makefile.in patch to fix the path to kernel headers
Created attachment 38672 [details]
New ebuild for davfs-0.2.2
I appended -r1 to make it work in my PORTDIR_OVERLAY. Dunno if you want to use
it as such.
Created attachment 40360 [details]
Ebuild with correct header
Former ebuild had incorrect CVS header (already filled out)
A bigger problem is that even with this patch davfs2 won't build if one has linux26-headers installed. :( Created attachment 42505 [details, diff]
Patch to make davfs build against 2.6
Bit more elegant patch for davfs2. Replaces the makefile patch and allows davfs
to build against a 2.6 kernel.
This takes care of both systems with a 2.6 kernel and 2.4 headers in
/usr/include, and systems with a 2.6 kernel and 2.6 headers in /usr/include.
No! This patch makes davfs (still) build against kernel headers in /usr/src/linux/include which you _never_ should. Use the headers in /usr/include/linux Read http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html for Linus' explanation about this issue. davfs 0.2.3 was released by upstream. See bug #70692 for details. I would leave 0.2.2 as is (only the security fix from 0.2.2-r1) applied and would recommend 0.2.3 to Kernel 2.6 users. Does 0.2.3 still suffer from this issue and is there still interest in fixing it? Whats the problem with having includes from /usr/src/linux if there is a working kernel? Thanks. I'll test 0.2.3 this evening. The problem with compiling userspace tools against the Kernel headers in /usr/src/linux/include is that they may change quite often, if the Kernel developers change interfaces, structs etc. (Yes, that happens) So if you install a new Kernel and the headers slightly changed: Boom! The userspace tools won't compile anymore. That's exactly what happened with davfs 0.2.2 The Kernel headers in /usr/include are specially modifed versions of the Kernel headers which may be used by userspace programs. Quoting Linus from http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html (It's 4 years old but I think it still applies): "The fact is, that the header files should match the library you link against, not the kernel you run on." Perhaps this package may be a special case since it uses the coda LKM. Maybe one of Gentoo's Kernel developers can give a better explanation or maybe I'm even completely wrong. You may want to set them CC on this bug (I won't do so since I'm not a Gentoo developer). We do no longer depend on the headers tanks to johnms patch. Fixed in cvs. |