> I found the problem. Patch linux-2.4.7-s390-3.diff was applied with=20
> ?dry-run, which means it was not actually applied. This patch is the one=20
> that creates the sysinfo.c.
>
> I apologize for jumping the gun. The scary part is this stuff is starting=20
> to make sense!
Time you got you
You haven't gotten to the scary part yet. That happens when you start
explaining things to others!
Mark Post
-Original Message-
From: Peter E. Abresch Jr. - at Pepco [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 23, 2002 7:29 PM
To: [EMAIL PROTECTED]
Subject: Re: sysinfo.o: No
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
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
