| 1 |
On Tue, Aug 15, 2017 at 6:04 PM, Rich Freeman <rich0@g.o> wrote: |
| 2 |
|
| 3 |
First, I appreciate your thoughts and comments. |
| 4 |
|
| 5 |
> |
| 6 |
> I suspect your sources have gotten messed up in some way. I've run |
| 7 |
> into issues like this when I do something like build a kernel with an |
| 8 |
> odd umask so that the portage user can't read the files it needs to |
| 9 |
> build a module. Your chmod should have fixed that but there could be |
| 10 |
> something else going on. It might just be that you didn't prepare the |
| 11 |
> sources? |
| 12 |
|
| 13 |
Same thought occurred to me, hence the chmod. Not sure what "prepare |
| 14 |
the sources" is all about; not a step I've ever used with kernels. |
| 15 |
But see below. |
| 16 |
|
| 17 |
> |
| 18 |
> I actually do all my kernel builds in a tmpfs under /var/tmp these |
| 19 |
> days which keeps my /usr/src/linux pristine. (make O=/var/tmp/linux |
| 20 |
> modules_install and so on) It does involve more building during |
| 21 |
> upgrades but I know everything is clean, and I prefer no-issues to |
| 22 |
> faster-builds. |
| 23 |
|
| 24 |
I have the same preference. Will have to take a look at following |
| 25 |
your example.. |
| 26 |
|
| 27 |
> |
| 28 |
> In theory that isn't essential, but I would definitely just wipe out |
| 29 |
> /usr/src/linux and unpack clean kernel sources. If you're using the |
| 30 |
> gentoo-sources package you can just rm -rf the symlink and the actual |
| 31 |
> tree, and just re-emerge the package and it will set up both. If |
| 32 |
> you're using git then I'd probably wipe it and re-pull as I'm not sure |
| 33 |
> if a clean/reset will actually take care of all the permissions. |
| 34 |
> |
| 35 |
> Then you need to run at least make oldconfig and make modules_prepare |
| 36 |
> before you can build a module against it. Doing a full kernel build |
| 37 |
> is also fine. |
| 38 |
|
| 39 |
I think I've done that (multiple times over the past 8 months). When |
| 40 |
a new kernel shows up as stable in the tree, I do (as root) |
| 41 |
|
| 42 |
emerge -DuNv gentoo-sources |
| 43 |
set up symlink |
| 44 |
cd into usr/src/linux |
| 45 |
zcat /proc/config.gz > .config |
| 46 |
make olddefconfig |
| 47 |
make menu_config (as a sanity check) |
| 48 |
make |
| 49 |
make modules_install |
| 50 |
make install |
| 51 |
|
| 52 |
I don't know what could have messed up the kernel tree other than |
| 53 |
whatever magic happens behind the scenes in the various make commands. |
| 54 |
|
| 55 |
Just now tried a make modules_prepare followed by an emerge -1 spl. Same error. |
| 56 |
|
| 57 |
Started again from scratch. Moved the kernel tree I've been working |
| 58 |
with (building kernel, modules, etc.) aside, then re-emerged |
| 59 |
gentoo-sources. Kernel tree should be pristine now, right? Then |
| 60 |
copied the config from my running kernel (same version 4.12.5) into |
| 61 |
/usr/src/linux. Then did a make modules_prepare. Finally did an |
| 62 |
emerge -1 spl. Same error as always. So, as attractive as the idea |
| 63 |
of a messed up kernel tree is to me, I don't think that's the source |
| 64 |
of the problem. |
| 65 |
|
| 66 |
I think it would be informative if I could somehow see exactly what |
| 67 |
commands are being run when the error occurs. Is there a way of doing |
| 68 |
that? |
| 69 |
|
| 70 |
John |
Archives