![]() I'm going to probably start digging into the source code of GNU patch and see where it's spinning, but thought I'd reach out to the community in the interim and see if somebody else had thoughts. Really curious as to what might be going wrong. I've watched nmon and don't actually see any memory use spikes at all during the few seconds that GNU patch spins before failing, and truss is silent during that 2-second wait as well. ![]() I'm also nervous about other potential future breakage elsewhere, since GNU patch works fine on other non-7.1 systems I have available. usr/bin/patch works fine, but that expects slightly differently-formatted patches (non-GNU AIX patch expects two leading columns in unified diffs), so to work with that, I have to manually reformat all patches. ![]() I also thought it might be the Toolbox RPM, so I rebuilt GNU patch from source and still have the same problem, so I think this has something to do with my system. ![]() I thought it might be my fix level, so I installed up to the newest service pack and rebooted, but still have the same issue. bash-5.1$ diff -u old/file.txt new/file.txt |tee diff.patch ![]() I first hit it trying to apply some patches for zeromq (context: I'm compiling it statically for software distribution to client machines that can't/won't install other RPMs), but found that even a simple contrived example triggers it: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |