Summary: | net-fs/openafs-kernel-1.4.14 does not build against 2.6.38 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dale Pontius <depontius> |
Component: | [OLD] Unspecified | Assignee: | Network Filesystems <net-fs> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | andrej.filipcic, bbaren, Bernd.Feige, bircoph, creffett, erict, orzel |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dale Pontius
2011-03-18 15:11:26 UTC
If you're feeling adventurous, you may want to give openafs-1.6.0_pre3 a try. It builds against 2.6.38 on my system, but I haven't gotten to testing it yet, so beware (i.e. take backups) - it's hard masked for a reason. i doubt upstream will ever fix this as dcache_lock has been removed in kernel 2.6.38. so we have no stable openafs in 2.6.38 in gentoo right now. i'm downgrading to 2.6.37 to hopefully build openafs against. i'm masking 2.6.38 on my systems. (In reply to comment #2) > i doubt upstream will ever fix this as dcache_lock has been removed in kernel > 2.6.38. > > so we have no stable openafs in 2.6.38 in gentoo right now. i'm downgrading to > 2.6.37 to hopefully build openafs against. i'm masking 2.6.38 on my systems. Isn't it easier to use 1.6.0_pre*? Works like a charm for me as a client on 2.6.38.x openafs 1.4.14 will only support kernels up to 2.6.37. Latest 1.6.0 prerelease is rather stable, but we cannot stabilize it until released. can't use unstable software for my critical systems, so no, using 1.6 isn't an option. looks like upstream has fixed this in 1.4.14.1 i'll try a version bump via my own ebuild. 1.4.14 against 2.6.37 seems extremely slow for somereason. unclear if it's because of the new vpn server we use, but file transfer in ftp is fine... (In reply to comment #4) > openafs 1.4.14 will only support kernels up to 2.6.37. Latest 1.6.0 prerelease > is rather stable, but we cannot stabilize it until released. isn't it possible to have the ebuild know about this ? such as a block or something ? (In reply to comment #6) > (In reply to comment #4) > > openafs 1.4.14 will only support kernels up to 2.6.37. Latest 1.6.0 prerelease > > is rather stable, but we cannot stabilize it until released. > > isn't it possible to have the ebuild know about this ? such as a block or > something ? Not easily done at all. The current ebuild looks at whatever kernel source is at /usr/src/linux, which may or may not be the source tree of the currently running kernel. In fact, there's a very good reason for the source tree to not match the currently running kernel, and that's when I'm running kernel N, have just finished building kernel N+1, and am running "modules-rebuild rebuild" so that the first boot of the new kernel should "just work" (TM). That said, I guess it would make sense to simply check against /usr/src/linux, since that's what's going to be used for the build. At the very least, an error message could be emitted and the build aborted faster, instead of churning and waiting until some compilation fails. 1.4.14.1 now in the tree |