story time: when my build system tried to gaslight me

[austanss]

Yes, I do very much mean gaslight me, in the actual definition of the word.
It lead me to alter my perception of reality.

I recently posted on here with a plethora of bugs, and nothing I tried could fix it.

I was lost for a whole two days.

I was starting to go insane, I had tried the same things over and over...

Was it the compiler optimizations???

Is my math right???

Am I calling this function???

Where are my breakpoints???????????

It was then that I realized, hey, my build system wasn't putting the newly-built kernel into the bin/ directory.

Alas, I try the new kernel, and all my issues are resolved.

[kzinti]

With time I have grown suspicious of this and similar problems. If it looks like my changes are not being picked up, I just delete my whole build directory just in case.

That said, you should still fix your build problems when you find them... It's been a while since I had one.

[eekee]

I had this on 9front once, with the added embarassment that it wasn't me who was writing the fixes. I was saying what was wrong, the kernel dev would write fixes, I'd pull compile reboot and nothing would be fixed! I wrote a little build script after that. 9ront kernel `mk install` doesn't install the new kernel to the actual boot partition on PCs. Neither does Bell Labs Plan 9, but I think it might work out better there: it loads a boot kernel which can hypothetically read Plan 9's native filesystems and kexec the real kernel. Emphasis on "might" and "hypothetically"; I don't recall if it's set up to do that by default.