Home → Stable →

Unable to update to gnupg-2.1.2 on 10.10.2 (make install failure, missing file)

• Edit

jim.luby

29 Mar, 2015 07:59 PM

gnupg-2.1.2
2.0.27b6

I was able to successfully run configure and make for gnupg-2.1.2 (Macintosh Yosemite) but I'm getting the following output upon trying to install the tools:

[jclMac:~/Desktop/gnupg-2.1.2] jcl% sudo make install Password:
Making install in m4
make[2]: Nothing to be done for install-exec-am'. make[2]: Nothing to be done forinstall-data-am'.
Making install in common
make install-am
make[3]: Nothing to be done for install-exec-am'. make[3]: Nothing to be done forinstall-data-am'.
Making install in kbx
../build-aux/install-sh -c -d '/usr/local/bin' /usr/bin/install -c kbxutil '/usr/local/bin' install: /usr/local/bin/kbxutil: No such file or directory
make[2]: *** [install-binPROGRAMS] Error 71
make[1]: *** [install-am] Error 2
make: *** [install-recursive] Error 1
[jclMac:~/Desktop/gnupg-2.1.2] jcl%

THANK YOU!

1. 1 Posted by jim.luby on 29 Mar, 2015 08:11 PM

   

   I should add that the reason I'm trying to get gnupg-2.1.2 installed is because in spite of trying various suggestions for allowing me to enter my passphrase in a Terminal/shell window, I cannot. Instead I have to enter the passphrase into a pinentry dialog box. This prevents me from using gpg in shell scripts, etc.

   • Edit

2. Support Staff 2 Posted by Luke Le on 01 Apr, 2015 03:32 PM

   

   Hi Jim,

   unfortunately we have not started working on integrating gnupg 2.1.x yet, but you could use it via homebrew.

   As for the pinentry dialog, did you already try to follow the instructions in this knowledge base article?
   https://gpgtools.tenderapp.com/kb/faq/how-to-enter-your-passphrase-...

   • Edit

3. 3 Posted by jim.luby on 01 Apr, 2015 09:49 PM

   

   Hi Luke,
   Thanks for responding to my call for help. I did try the approach
   wherein $PINENTRY_USER_DATA
   USE_CURSES=1 but that didn't seem to work for me. I've pasted some
   debug information below (delimited by the lines of pound signs) in case
   it is helpful.

   Best regards,

   Jim

   #################################################################
   bash-3.2$ gpg2 --version
   gpg (GnuPG) 2.1.2
   libgcrypt 1.6.3
   Copyright (C) 2015 Free Software Foundation, Inc.
   License GPLv3+: GNU GPL version 3 or later
   <http://gnu.org/licenses/gpl.html>
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.

   Home: ~/.gnupg
   Supported algorithms:
   Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
   Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
            CAMELLIA128, CAMELLIA192, CAMELLIA256
   Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
   Compression: Uncompressed, ZIP, ZLIB, BZIP2
   #################################################################

   #################################################################
   bash-3.2$ echo $PINENTRY_USER_DATA
   USE_CURSES=1
   #################################################################

   #################################################################
   bash-3.2$ cat test
   hello world
   #################################################################

   #################################################################
   bash-3.2$ gpg2 -c < test > test.gpg
   gpg: can't connect to the agent: IPC connect call failed
   gpg: problem with the agent: No agent running
   gpg: can't connect to the agent: IPC connect call failed
   gpg: problem with the agent: No agent running
   gpg: error creating passphrase: Operation cancelled
   gpg: symmetric encryption of '[stdin]' failed: Operation cancelled
   #################################################################

   • Edit

4. 4 Posted by Ben on 03 Apr, 2015 12:31 PM

   

   To get GPG 2.1.2 working on a system with GPGTools and maintain an older version (1.4.19), this works:

   1) Install GPG 1.4.x in /usr/local/ (standard configure && make && make install).

   2) Make a copy of ~/.gnupg/ to something like ~/.gnupg2/

   3) Install GPGTools as normal.

   4) /usr/local/bin/gpg2 will be a symlink to /usr/local/MacGPG2/bin/gpg2 so delete /usr/local/bin/gpg2

   5) Install GPG 2.1.2 using MacPorts and tell it to compile everything from source: sudo port -v -s install gnupg21

   • This has a lot of dependencies and will take a while.
   • When it is done it will be installed to /opt/local/bin/gpg2

   6) Create a bash script which contains the following: exec /opt/local/bin/gpg2 --homedir $HOME/.gnupg2 "$@"

   • This will call GPG 2.1 in such a way that it does not convert the original config files in ~/.gnupg, but allows you to use the gpg2 command normally.
   • Using this with Enigmail is simply a matter of changing the preferences to use /usr/local/bin/gpg2 instead of /usr/local/bin/gpg (the default).
   • GPGTools should continue to call the same file (which is why it created the symlink in the first place, because /usr/local/bin is already in your path and /usr/local/MacGPG2 is not)

   None of the above covers customising any of the versions installed, but that's usually just a case of recompiling or compiling a new version in some other location (though usually relying on the libraries installed with the MacPorts version) and then updating the shell script to point to that instead.

   Depending on which programs have already been used you may or may not need to (or want to) update the gpg-agent.conf file to specify a particular pinentry program to use with gpg-agent. If there is more than one person using the system, this will work for all users (just as long as the GPG home directories are in the same locations in each user account). And here's the result as it appears for me with the only thing I have to worry about is remembering to import new keys into both GPG 1.4 and GPG 2.1.

   bash4-4.3$ which gpg
   /usr/local/bin/gpg
   bash4-4.3$ ls -l /usr/local/bin/gpg
   -rwxr-xr-x  1 root  admin  1136964  3 Apr 22:14 /usr/local/bin/gpg
   bash4-4.3$ file /usr/local/bin/gpg
   /usr/local/bin/gpg: Mach-O 64-bit x86_64 executable
   bash4-4.3$ which gpg2
   /usr/local/bin/gpg2
   bash4-4.3$ ls -l /usr/local/bin/gpg2
   -rwxr-xr-x  1 root  admin  194 29 Mar 23:30 /usr/local/bin/gpg2
   bash4-4.3$ file /usr/local/bin/gpg2
   /usr/local/bin/gpg2: Bourne-Again shell script, ASCII text executable
   bash4-4.3$ ls -l /opt/local/bin/gpg2
   -rwxr-xr-x  1 root  admin  917612  3 Apr 21:15 /opt/local/bin/gpg2
   bash4-4.3$ file /opt/local/bin/gpg2
   /opt/local/bin/gpg2: Mach-O 64-bit x86_64 executable
   bash4-4.3$ ls -l /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac
   -rwxr-xr-x  1 root  wheel  145568 18 Mar 23:52 /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac
   bash4-4.3$ file /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac
   /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac: Mach-O 64-bit x86_64 executable
   bash4-4.3$ ls -l /Applications/MacPorts/pinentry-mac.app/Contents/MacOS/pinentry-mac
   -rwxr-xr-x  1 root  wheel  76108  3 Apr 19:24 /Applications/MacPorts/pinentry-mac.app/Contents/MacOS/pinentry-mac
   bash4-4.3$ file /Applications/MacPorts/pinentry-mac.app/Contents/MacOS/pinentry-mac
   /Applications/MacPorts/pinentry-mac.app/Contents/MacOS/pinentry-mac: Mach-O 64-bit x86_64 executable
   bash4-4.3$ gpg --version
   gpg (GnuPG) 1.4.19
   Copyright (C) 2015 Free Software Foundation, Inc.
   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.
   
   Home: ~/.gnupg
   Supported algorithms:
   Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
   Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
           CAMELLIA128, CAMELLIA192, CAMELLIA256
   Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
   Compression: Uncompressed, ZIP, ZLIB, BZIP2
   bash4-4.3$ gpg2 --version
   gpg (GnuPG) 2.1.2
   libgcrypt 1.6.3
   Copyright (C) 2015 Free Software Foundation, Inc.
   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.
   
   Home: /Users/username/.gnupg2
   Supported algorithms:
   Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
   Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
           CAMELLIA128, CAMELLIA192, CAMELLIA256
   Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
   Compression: Uncompressed, ZIP, ZLIB, BZIP2
   bash4-4.3$
   

   • Edit

5. 5 Posted by jim.luby on 03 Apr, 2015 02:17 PM

   

   Hi Ben,
   Thanks for your notes. Using brew, I was able to install gpg 2.1.2.
   What I've not been able to get working is the following (second note I
   posted on the web page):

   > I should add that the reason I'm trying to get gnupg-2.1.2 installed
   > is because in spite of trying various suggestions for allowing me to
   > enter my passphrase in a Terminal/shell window, I cannot. Instead I
   > have to enter the passphrase into a pinentry dialog box. This prevents
   > me from using gpg in shell scripts, etc.

   Have you been able to use "gpg2 -c < plainTextFile > encryptedFile.gpg"
   to encrypt a file AND have the code prompt for the passphrase in the
   Terminal (shell) window? When I try this command I get the following
   results:

   > gpg: can't connect to the agent: IPC connect call failed
   > gpg: problem with the agent: No agent running
   > gpg: can't connect to the agent: IPC connect call failed
   > gpg: problem with the agent: No agent running
   > gpg: error creating passphrase: Operation cancelled
   > gpg: symmetric encryption of '[stdin]' failed: Operation cancelled

   When I try the same command with gpg (i.e. not gpg2), I get the
   following prompt in the Terminal window:
   > [jclMac:~] jcl% gpg -c < test > test.gpg
   > Enter passphrase:

   Thanks!

   Jim

   • Edit

6. 6 Posted by Ben on 03 Apr, 2015 03:19 PM

   

   Try this instead:

   echo "Some text or whatever" | gpg -c > gpgtest-1.gpg
   echo "Some other text or whatever" | gpg2 -c > gpgtest-2.gpg

   • signature.asc 631 Bytes
   • Edit

7. 7 Posted by jim.luby on 03 Apr, 2015 10:33 PM

   

   Hi Ben,
   I tried your suggestion to pipe text into gpg2 but got the same error as
   follows:

   > [jclMac:~] jcl% which gpg2
   > /usr/local/bin/gpg2
   > [jclMac:~] jcl% gpg2 --version
   > gpg (GnuPG) 2.1.2
   > libgcrypt 1.6.3
   > Copyright (C) 2015 Free Software Foundation, Inc.
   > License GPLv3+: GNU GPL version 3 or later
   > <http://gnu.org/licenses/gpl.html>
   > This is free software: you are free to change and redistribute it.
   > There is NO WARRANTY, to the extent permitted by law.
   >
   > Home: ~/.gnupg
   > Supported algorithms:
   > Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
   > Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
   > CAMELLIA128, CAMELLIA192, CAMELLIA256
   > Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
   > Compression: Uncompressed, ZIP, ZLIB, BZIP2
   > [jclMac:~] jcl%
   > [jclMac:~] jcl%
   > [jclMac:~] jcl% echo "Some other text or whatever" | gpg2 -c >
   > gpgtest-2.gpg
   > gpg: can't connect to the agent: IPC connect call failed
   > gpg: problem with the agent: No agent running
   > gpg: can't connect to the agent: IPC connect call failed
   > gpg: problem with the agent: No agent running
   > gpg: error creating passphrase: Operation cancelled
   > gpg: symmetric encryption of '[stdin]' failed: Operation cancelled
   > [jclMac:~] jcl%

   Cheers,

   Jim

   • Edit

8. 8 Posted by Ben on 04 Apr, 2015 05:15 AM

   

   Try this then:

       ps auxww | grep gpg-agent

   The output should be three lines, one containing something like
   "gpg-agent --use-standard-socket --daemon", the next with "/bin/bash
   /usr/local/MacGPG2/libexec/shutdown-gpg-agent" and the last with the
   command just run "grep gpg-agent".

   If there are no lines or just the last one then either gpg-agent needs
   to be started or it is having problems running. Since it is bundled
   with GPG 2.1.2 then it is possible that there is a flaw with the
   homebrew build. And, given it's homebrew, when I say possible I really
   mean likely. Homebrew may claim to have more packages, but MacPorts is
   far more reliable with what it does have (and what it does have is
   enough to build *everything* else).

   Anyway, if gpg-agent is not running, try running this command:

       gpg-agent --use-standard-socket --daemon

   Also check your gpg-agent.conf file and make sure it includes the
   following two lines:

       log-file ~/Logs/gpg-agent.txt
       debug-level guru

   This will create a Logs/ directory in your ~/.gnupg/ directory which
   contains debugging information about gpg-agent if it runs.

   • signature.asc 631 Bytes
   • Edit

9. 9 Posted by jim.luby on 04 Apr, 2015 03:49 PM

   

   Hi Ben,
   Thanks for your continued help on this problem. Below is what I got upon
   checking the process listing:

   > [jclMac:~] jcl% ps auxww | grep gpg-agent
   > jcl 401 0.0 0.0 2434392 928 ?? S 3:06PM
   > 0:00.01 /bin/bash /usr/local/MacGPG2/libexec/shutdown-gpg-agent

   > [jclMac:~] jcl% gpg-agent --use-standard-socket --daemon
   > Assertion failed: (!res), function leave_npth, file npth.c, line 129.
   > Abort

   > [jclMac:~] jcl% sudo kill -HUP 401
   > Password:

   > [jclMac:~] jcl% gpg-agent --use-standard-socket --daemon
   > Assertion failed: (!res), function leave_npth, file npth.c, line 129.
   > Abort

   Perhaps the easiest thing for me to try next is try to use macports for
   the installation. As you say, it could be a brew install-related problem.

   Thanks,

   Jim

   • Edit

10. 10 Posted by Ben on 04 Apr, 2015 04:19 PM

    

    Well, npth is one of the dependencies of GPG 2.1 and if it hasn't been
    compiled correctly by brew (not surprising, it's a little fiddly with
    them because they must be done in a very specific order) then things
    will definitely break.

    As for brew vs. macports, well, brew is a ruby based project to try to
    shoe-horn compiling anything on os x in the most general way possible
    (to get more stuff faster). Whereas MacPorts is essentially a port of
    the FreeBSD package management system. It's a little more robust (and
    still has *plenty* of stuff).

    For my part I turned my back on Homebrew with my old MBP on OS X 10.5
    when it told me I could not install my own compiled version of Python or
    the official Python release from python.org; it was its way or the
    highway. So I introduced it to the "srm -rfmz" command (secure delete).

    • signature.asc 631 Bytes
    • Edit

11. 11 Posted by jim.luby on 04 Apr, 2015 04:22 PM

    

    Thanks, again, Ben. I'll move on to macports and see how things go. I've
    used both macports and fink in the past but decided to try brew
    recently. Brew has worked well for some packages.

    Cheers,

    Jim

    • Edit

12. Support Staff 12 Posted by Steve on 14 Aug, 2015 12:49 PM

    

    I have attached our ticket to integrate gnupg 2.1 so you'll be notified if there are news in that regard.

    Closing this discussion for the time being. You can always re-open if you want.

    • Edit

13. Steve closed this discussion on 14 Aug, 2015 12:49 PM.

14. Steve re-opened this discussion on 13 Jun, 2017 08:41 PM

15. Support Staff 13 Posted by Steve on 13 Jun, 2017 08:41 PM

    

    Hi Jim and Ben,

    we have a first GPG Suite test build which integrates gpg 2.1. Here is the signature file for that release.

    It would be great if you could test this build and let us know if run into any trouble. Please note, that downgrading to the current beta release will require additional steps in case new keys were created using this test build. Depending on the test results, gpg 2.1 may soon land in the beta branch.

    All the best,
    steve

    • Edit

16. 14 Posted by jim.luby on 14 Jun, 2017 12:49 PM

    

    Hi Steve,
    My Mac system failed about 6 months ago and I decided then to switch to
    linux so I'm not in a position to test the new Mac GPG suite.

    Best regards,

    Jim

    • Edit

17. Support Staff 15 Posted by Steve on 14 Jun, 2017 01:35 PM

    

    Thanks for the feedback. No problem at all. I'll close this. If you Ben, have any feedback just re-open anytime.

    • Edit

18. Steve closed this discussion on 14 Jun, 2017 01:35 PM.

19. Steve closed this discussion on 18 Jun, 2017 05:30 PM.