documentation: Avoid too tight binary dependency

[Andreas Metzler]

Hello,

find attached a trivial patch against GIT master to stop suggesting
gcry_check_version (GCRYPT_VERSION)
since this will fail incorrectly. e.g. a binary built against 1.8.4
does run perfectly well against libgcrypt 1.8.3.

Instead let's suggest doing what gnupg2 does, specifying the version
that is needed to build successfully.

Thanks for considering, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-doc-Fix-library-initialization-examples.patch
Type: text/x-diff
Size: 1836 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gcrypt-devel/attachments/20181118/7a640b52/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gcrypt-devel/attachments/20181118/7a640b52/attachment.sig>