F35KER%DHHDESY3.BITNET@cunyvm.cuny.edu (Kerst van Raden) (02/07/90)
Hi everybody! While upgrading my system to ST 1.5.0 I ran into the following problem: I had unpacked the cdiffs in the src/fs directory and tried to patch the 1.1 files. I entered for i in *.cdif; do patch <$i ; done . patch processed most of the diffs without error but it broke on 8 of them with messages that said something like: |*** anyfile.xyz |--- anyotherfile.xyz ------------------------ Patching file anyotherfile.xyz using Plan A ... Hunk #1 succeeded at 4. Hunk #2 succeeded at 10. Hunk #3 succeeded at 15. Hunk #4 succeeded at 25. Hmm... The next patch looks like a new-style context diff to me... The text leading up to this was: -------------------------------- |- -------------------------------- and then there is an error message saying,that it can't patch this file. I have tried this with a patch 2.0 patchlevel 12 that I got from the net some months ago, compiled with the PC 1.4a lib and with a binary of patch 2.0 patchlevel 11 that was posted as official ATARI patch. The output is almost the same except that 2.0#12 just quits, while the 2.0#11 asks for a file to patch. I could not compile the version delivered with the upgrade package yet because there is some header missing in ST 1.1 (as for as i remember while typing this). Has anybody else had this problem when doing the upgrade? And is there a quick remedy? Kerst van Raden @ Deutsches Elektronen-Synchrotron Hamburg F35KER@DHHDESY3.BITNET
bradr@uwovax.uwo.ca (02/08/90)
In article <10401@nigel.udel.EDU>, F35KER%DHHDESY3.BITNET@cunyvm.cuny.edu (Kerst van Raden) writes: > Hi everybody! > While upgrading my system to ST 1.5.0 I ran into the following problem: > I had unpacked the cdiffs in the src/fs directory and tried to patch > the 1.1 files. I entered > for i in *.cdif; do patch <$i ; done . > patch processed most of the diffs without error but it broke on 8 of > them with messages that said something like: > |*** anyfile.xyz > |--- anyotherfile.xyz > ------------------------ > Patching file anyotherfile.xyz using Plan A ... > Hunk #1 succeeded at 4. > Hunk #2 succeeded at 10. > Hunk #3 succeeded at 15. > Hunk #4 succeeded at 25. > Hmm... The next patch looks like a new-style context diff to me... > The text leading up to this was: > -------------------------------- > |- > -------------------------------- > > and then there is an error message saying,that it can't patch this file. > I had this problem too. If you have been following the upgrade directions in order then by now you will have created the new library libc.a. Try recompiling patch now and it should be fine. Apparently, there were some bugs in the original library that show up in patch. regards, brad
UK0W%DKAUNI2.BITNET@cunyvm.cuny.edu (Stefan Haenssgen) (02/08/90)
hi there... > Kerst van Raden (F35KER@DHHDESY3.BITNET) writes: > While upgrading my system to ST 1.5.0 I ran into the following problem: > I had unpacked the cdiffs in the src/fs directory and tried to patch > the 1.1 files. I entered ....... > Hmm... The next patch looks like a new-style context diff to me... > The text leading up to this was: > -------------------------------- > |- > -------------------------------- > > and then there is an error message saying,that it can't patch this file. > Has anybody else had this problem when doing the upgrade? And is there > a quick remedy? I had exactly the same problem. It disappeared when I recompiled patch using the new libraries (strange indeed). However, i still have some problems with 1.5: - The strncpy() routine doesn't seem to work all the time. Someone told me that there was a patch for it, could some- body re-post it please? - I get lots of ".. panic Exit via trap 6" at irregular intervals. I couldn't reproduce the exact circumstances, but they keep appearing during compilation, listing files etc. This is still under Minix 1.1, so maybe it will get better with 1.5 - Compiling the kernel, mm & fs results in many warnings about pointers (conversion to integer loses accuracy, conversion to long.., incompatible pointers in =, etc). Is this because the PC 1.5 assumes that pointer=integer=long? I ignored the warnings, but I don't like them at all. Has anybody succeeded in installing the new 1.5 on his ST, with- out cross-compiling from GNU-C or other "tricks"? It is DEFINITELY NOT possible to patch an ORIGINAL 1.1 Version directly to 1.5: not only programs like sed are missing in the 1.1 package, but it is also necessary to include some of the new library routines in order to compile the new programs. I have managed to compile a 1.5 minix.img using just the standard minix compiler and the new libraries, but it doesn't work very well... I get a nice "Memory Fault - Core dumped" as soon as I log in, and "ls" results in another core dump... well, at least "rm core" works ;-) I guess that the old strncpy() is to blame, but there seem to be lots of other bugs left. I wonder how many fixes will be needed before 1.5 runs smoothly - has anyone kept track of all the postings that dealt with bug fixes? Since most of them aren't "official" anyway, i am afraid that there are 1001 different versions of 1.5 (and this doesn't make updates easier). Keep patching, Stefan _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+ Stefan Haenssgen Universitaet Karlsruhe UK0W@DKAUNI2.BITNET _+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+