Hi,
Kernels built against the vger tree from Monday
morning no longer boot on my 4/330. Everything
seems OK until it tries to fire up init at which
point ld-linux.so.2 (or whatever - it's from UP
1.1) barfs with an undefined symbol, which seems
to vary, but is often strlen (sometimes without
the n at the end).
I don't remember the last time I tried a vger kernel
on this box, but it definitely works fine with
2.2.4ac1 (plus a couple of compilation fixes).
I note that a lot of Jakub's changes to mm/memory.c
seem to be in - are they likely to cause exec/mmap
breakages?
Matthew.
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
