Tyler, all,
I did some investigating of this problem, and it looked like the original
linux-2.4.17-s390.tar.gz file had gotten clobbered by something much larger
than it should have been. I send an email to [EMAIL PROTECTED] yesterday,
and got a response today from Tuan that the problem had been corrected. I
re-downloaded all the patches,
linux-2.4.17-s390.tar.gz
linux-2.4.17-s390-1-lcs.tar.gz
linux-2.4.17-s390-2.tar.gz
linux-2.4.17-s390-kerntypes.tar.gz
and applied them on the "pure" kernel source from kernel.org. They went on
fine, I just got a few "offset" and "fuzz" messages out when I put on the
lcs patch:
patch -p0 < linux-2.4.17-s390-1-lcs.diff
patching file linux-2.4.17/arch/s390/defconfig
Hunk #1 succeeded at 123 (offset -2 lines).
patching file linux-2.4.17/arch/s390x/defconfig
Hunk #1 succeeded at 123 (offset -2 lines).
patching file linux-2.4.17/drivers/s390/Config.in
patching file linux-2.4.17/drivers/s390/net/Makefile
Hunk #1 succeeded at 12 with fuzz 2.
patching file linux-2.4.17/drivers/s390/net/lcs.c
The compile goes well until gas chokes on an stsi opcode. Apparently the
binutils I have on my Slackware/390 system aren't recent enough to handle
it. So, for anyone that was interested in the 2.4.17 release, it looks like
the patches are in good order again, and I would recommend giving them
another try.
Mark Post
-----Original Message-----
From: Tyler Koyl [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 12:29 PM
To: [EMAIL PROTECTED]
Subject: 2.4.17 Patches -> Problems applying
Trying to build the proper kernel source tree for 2.4.17 available on the
IBM developer works site. Specifically the following:
linux-2.4.17.tar.gz (original kernel source)
+ linux-2.4.17-s390.diff (IBM)
+ linux-2.4.17-s390-1-lcs.diff (IBM)
+ linux-2.4.17-s390-2.diff (IBM)
The first one works great. but linux-2.4.17-s390-1-lcs.diff does not go
very cleanly. This is what I got:
# patch -p0 < /home/tkoyl/2.4.17/linux-2.4.17-s390-1-lcs.diff
patching file linux-2.4.17/arch/s390/defconfig
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 162 (offset 37 lines).
patching file linux-2.4.17/arch/s390x/defconfig
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 162 (offset 37 lines).
patching file linux-2.4.17/drivers/s390/Config.in
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file linux-2.4.17/drivers/s390/net/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n] y
The next patch would create the file linux-2.4.17/drivers/s390/net/lcs.c,
which already exists! Assume -R? [n] y
patching file linux-2.4.17/drivers/s390/net/lcs.c
Hunk #1 FAILED at 1.
File linux-2.4.17/drivers/s390/net/lcs.c is not empty after patch, as
expected
1 out of 1 hunk FAILED -- saving rejects to file
linux-2.4.17/drivers/s390/net/lcs.c.rej
Not sure what is happening with the lcs.c file here. Within the patch it
looks like a complete rewrite of the file.
Has anyone run into this and have a possible solution?
Thanks,
Tyler Koyl
Software Support Specialist
Saskatchewan Wheat Pool
Regina, Saskatchewan, Canada
