| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
LibreSSL's pc files effectively hardcode the version to 1.0.0 since
LibreSSL exists. That probably never made much sense. This causes
some pain for ports that "need 'openssl' ['>= +1.1.0'] found '1.0.0'"
or similar while they would build perfectly fine with LibreSSL.
This only affects OpenBSD. We do not put the actual LibreSSL version
in there since it may cause trouble
Discussed with sthen, millert, inoguchi, beck over the past year.
Diff from/ok sthen
|
|
|
|
|
|
|
|
| |
In libssl.pc, Libs: should not have '-lcrypto', and Requires.private:
should have it as 'libcrypto'.
openssl.pc does not need Libs: and Cflags:, but should have Requires:.
OK millert@
|
| |
|
|
|
|
|
|
|
|
|
| |
as configuration files; split manpages and .pc files between libcrypto and
libssl.
No functional change, only there to make engineering easier, and libcrypto
sources are still found in libssl/src/crypto at the moment.
ok reyk@, also discussed with deraadt@ beck@ and the usual crypto suspects.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the openssl and libz versions:
- use a generic ${lib_version}
- define ${version_file} to look run ${version_re} on to
acquire the library version.
- add license
- remove unused -k flag
no change in generated files
ok sthen@
|
|
|
|
| |
ok sthen@
|
|
|
|
| |
Fixes build on NFS src with no root access. ok jasper@
|
|
|
|
|
|
|
| |
test -n "`pkg-config --cflags openssl`"
don't assume that OpenSSL isn't available.
ok miod@, sthen@, ajacoutot@, djm@
|
|
|
|
| |
prompted by brad
|
|
|
|
| |
- zap a trailing tab
|
|
projects depend on being present (e.g. various ports).
as discussed with various porters in a hungarian spa
help/feedback from ingo@ and also OK halex@
no objections from djm@
|