HOWTO: Patch (discussion)
This didn't belong in eq4me's thread about the gcc4.1 patch, but sorta applies to it in general... I want no trout smackinz!!
To the matter...
eq4me, your patch definitely fixes the compile problems I have in FC5 with gcc4.1 - so bravo, thank you for that. However, using "patch < diff.patch" refused to work for me no matter what I did. I saw some lines that might have been broken, thought I fixed them, to no avail. I did go line-by-line and get all the changes in, and compiled successfully. /cheer!
Can I beg for one more scrap of info? Something I have not been able to find here yet is a precise "this is exactly what to type" command for using a patch file to update your local source.
Wikipedia showed me "patch < [patch file name]", but in this case I kept getting errors that it could not find the destination file, and prompted me for the file name. When entering a name, it thought the file was already patched and wanted to revert it (-R). If I did that, it just stopped working.
So here's info I could use, and might help others who have questions about source patching.
- Is there a specific source/destination folder structure needed? (ie, /orig-source, /new-source, etc) or will any old name do?
- What directory must the patch live in? Say, /home/build/patchfile, with the source directories under that?
- Is "patch" the only command line needed, or should we use --strip or other params to apply these diffs?
The end result I am seeking is, take a patch file/post from here, paste it into a file on *NIX, and simply patch the emu source. Thanks in advance for any input or time to explain this to the Linux newbies in the crowd.
J
|
Threaded Mode
