I found the problem. Patch linux-2.4.7-s390-3.diff was applied with
?dry-run, which means it was not actually applied. This patch is the one
that creates the sysinfo.c.
I apologize for jumping the gun. The scary part is this stuff is starting
to make sense!
Thanks everyone.
Peter
Peter E Abresch
05/23/2002 06:33 PM
To: Linux on 390 Port <[EMAIL PROTECTED]>
cc:
Subject: sysinfo.o: No such file or directory
We applied IBM's patch linux-2.4.7-s390-3.diff through
linux-2.4.7-s390-7.diff to SuSE's 2.4.7 kernel. All appeared to go well
except the "make image" fails with "ld: cannot open sysinfo.o: No such
file or directory".
A find command cannot find sysinfo.o or sysinfo.c. This problem was
introduced with patch linux-2.4.7-s390-4.diff that added it to
/usr/src/linux/drivers/s390/Makefile.
Any ideas how to continue? Thanks for any info.
Peter
