On 12/04/2013 03:58 PM, Bernhard Voelker wrote: > On 12/04/2013 02:45 PM, Pádraig Brady wrote: >> On 12/04/2013 01:39 PM, Bernhard Voelker wrote: >>> --with-openssl The coreutils default is: --with-openssl=optional >>> --with-openssl use libcrypto hash routines. Valid ARGs are: >>> 'yes', >>> 'no', 'optional' => use if available >> >> I've documented the reason for that at least in configure.ac: >> >> dnl Enable use of libcrypto if available. >> dnl Note we could do this as follows: >> dnl AS_VAR_SET_IF([with_openssl], [], [with_openssl=optional]) >> dnl However that would not document the coreutils adjusted default, >> dnl so we add another --with-openssl description just to document that >> >> It's the best I could come up with for now, >> and I don't think it's too bad? > > Well, I think it's confusing because of the names: > 'openssl' and 'libcrypto' (shouldn't the latter be 'libgcrypt'?) are > distinct packages on an actual system, so I don't see how a user may > choose between them with 'yes'|'no'|'optional'. > What do I miss?
I shouldn't have mixed the names, but they're synonymous for me: $ rpm -qf /usr/lib64/libcrypto.so openssl-devel...
