Summary: | sys-fs/zfs interactively runs oldconfig in kernel source tree | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | griffgd |
Component: | [OLD] Core system | Assignee: | Richard Yao (RETIRED) <ryao> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | griffgd |
Priority: | Low | Keywords: | Bug, UPSTREAM |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
FEATURES="--sandbox --usersandbox" emerge --info sys-fs/zfs
build.log for FEATURES="-sandbox -usersandbox" emerge sys-fs/zfs |
Description
griffgd
2012-09-04 15:07:32 UTC
Please attach the entire build log to this bug report. Created attachment 322926 [details]
build.log for FEATURES="-sandbox -usersandbox" emerge sys-fs/zfs
Wouldn't this happen only when the source trees in question haven't been previously configured? One would assume yes, however, the kernel tree was configured, built and running before getting this error. An moving from 3.4.9 to 3.5.3 was also done, with a make oldconfig run and all options resolved, specifically the one that seems to be causing the error. Issue resolved. KERNEL_DIR was set to /usr/src/linux in make.conf. sys-fs/zfs seems to use this as an override for something related to the kernel. It would be good to note somewhere that this behavior is happening, preferably right where it would start deviating from normal behavior by attempting to write to/build at the location KERNEL_DIR refers to. (In reply to comment #5) > Issue resolved. > > KERNEL_DIR was set to /usr/src/linux in make.conf. sys-fs/zfs seems to use > this as an override for something related to the kernel. > > It would be good to note somewhere that this behavior is happening, > preferably right where it would start deviating from normal behavior by > attempting to write to/build at the location KERNEL_DIR refers to. This is an upstream bug. I will leave it open, but I am too busy to work on it right now. I have informed upstream about this, but I expect that this will be a low priority for them too. (In reply to comment #6) > This is an upstream bug. I will leave it open, but I am too busy to work on > it right now. I have informed upstream about this, but I expect that this > will be a low priority for them too. I did not understand autotools at the time this bug was filed. That has since changed and I have sent a patch upstream to address this issue: https://github.com/zfsonlinux/zfs/pull/1151 I will backport it to sys-fs/zfs after upstream accepts it. I regret not fixing this sooner. This bug has been fixed since sys-fs/zfs-kmod-0.6.0_rc13 entered the tree on December 23. I did not backport it because it was rolled into the next release by upstream shortly after being accepted. |