Thank you! That -pnum option threw me. So, I successfully compiled the app. Here’s the problem, it did not replace my system mutt, but simply installed it in the directory in Downloads. I haven’t had a program do that before. Did I need to remove the old mutt and maybe place the files in there before building, or did I miss a step? (Do you need more info to proceed?)
Best, Conor Cook > On Feb 3, 2015, at 10:37 AM, Vincent Lefevre <[email protected]> wrote: > > On 2015-02-03 08:36:36 -0600, Conor Cook wrote: >> I suppose this is why I am wondering if I should be emailing through >> the regular mail list, rather than dev, because I’m not quite sure >> what to do with the patch. I managed to find the patch command, but >> when I run 'patch <patch-1.5.21hg.tamovl.sysdotlock.1’, I get: >> >> patching file Makefile.am >> patching file configure.ac >> patching file Makefile.am >> Hunk #1 FAILED at 2. >> 1 out of 1 hunk FAILED -- saving rejects to file Makefile.am.rej >> patching file init.h > > You need to use the -p1 option: > > patch -p1 < patch-1.5.21hg.tamovl.sysdotlock.1 > > Then > > autoreconf > > to rebuild the "configure" script. Several GNU development utilities > need to be installed: autoconf, automake, and perhaps others. > > -- > Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> > 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> > Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
