> 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).

Weird. My 4/330 is running a kernel compiled with vger CVS including
the SMP patches I added yesterday. It is fine. 

Anton
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]

Reply via email to