On Mon, Jan 08, 2007 at 10:38:46PM +0100, Frederik Schueler wrote:
> Looking at what happened to the last 2.6.20rc4 snapshots - build logs
> are here:
I found the source of the problem.
Our own code fails with:
| rm: cannot remove
`/build/buildd/17438-0/linux-2.6-2.6.20~rc4/debian/linux-image-2.6.20-rc4-486/lib/modules/2.6.20-rc4-486/build':
No such file or directory
It tries to remove something which should be there always.
Some lines up, the kernel supplied makefiles executes depmod.
| if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map
-b /build/buildd/17438-0/linux-2.6-2.6.20~rc4/debian/linux-image-2.6.20-rc4-486
-r 2.6.20-rc4; fi
But the used release info is wrong. Now it is clear that it uses the
wrong info through the whole build.
linux-2.6 uses a localversion file to append the flavour informations to
the upstream version. There is a comment in the code which says
| # skip backup files (containing '~')
and our version contains one, so it just ignores anything.
Bastian
--
Where there's no emotion, there's no motive for violence.
-- Spock, "Dagger of the Mind", stardate 2715.1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
