Skip to contentSkip to conversation

Make clean misses stuff in 2.6.0-test4.

DISCUSSION Rob Landley 2 participants 3 messages Sep 1, 2003 – Sep 2, 2003

lore
Share & tools
lore
#0 lore raw

I did a build as root, did a make clean (still as root), and then kicked off a build as my normal user account:

It died:

rm: cannot remove `.tmp_versions/cryptoloop.mod': Permission denied
rm: cannot remove `.tmp_versions/orinoco.mod': Permission denied
rm: cannot remove `.tmp_versions/hermes.mod': Permission denied
rm: cannot remove `.tmp_versions/orinoco_cs.mod': Permission denied
rm: cannot remove `.tmp_versions/orinoco_tmd.mod': Permission denied
rm: cannot remove `.tmp_versions/snd-seq-midi.mod': Permission denied
rm: cannot remove `.tmp_versions/snd-rawmidi.mod': Permission denied
rm: cannot remove `.tmp_versions/snd-mpu401-uart.mod': Permission denied
rm: cannot remove `.tmp_versions/snd-ac97-codec.mod': Permission denied
rm: cannot remove `.tmp_versions/snd-ali5451.mod': Permission denied

Rob

#1 lore raw
Quoted 6 lines · Rob Landley

I did a build as root, did a make clean (still as root), and then kicked off a build as my normal user account:

It died:

rm: cannot remove `.tmp_versions/cryptoloop.mod': Permission denied

The directory .tmp_versions is not deleted by 'make clean'. For that you need 'make mrproper'.

Sam

#2 lore raw
Quoted 4 lines · Sam Ravnborg
Quoted 3 lines · Rob Landley

I did a build as root, did a make clean (still as root), and then kicked off a build as my normal user account:

Quoted 8 lines
Quoted 3 lines

It died:

rm: cannot remove `.tmp_versions/cryptoloop.mod': Permission denied

The directory .tmp_versions is not deleted by 'make clean'. For that you need 'make mrproper'.

Sam

Which zaps the .config, last time I tried it. (Just tried it again and yup, it zapped it.)

Interestingly, I forgot that make install doesn't install modules (for that you need make modules_install), but it DOES try to re-index them (resulting in some complaints about the modules for the smp kernel I'd accidentally compiled earlier having unresolved symbols in them). I misinterpreted this as it complaining that the *.ko files in the build tree hadn't been updated, and did a "find . -name '*.ko' | xargs rm", and at that point the build process's dependencies got confused enough I just did a make clean and started over...

Don't mind me, I'm having fun...

Rob