<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/generate_pkgconfig.sh, branch OPENBSD_7_9_BASE</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2022-02-04T16:42:15+00:00</updated>
<entry>
<title>Bump libressl's version in pkgconfig to 2.0.0</title>
<updated>2022-02-04T16:42:15+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-02-04T16:42:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=54b37ce29213d429a1f20782418b17863e8b4b9b'/>
<id>urn:sha1:54b37ce29213d429a1f20782418b17863e8b4b9b</id>
<content type='text'>
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' ['&gt;= +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
</content>
</entry>
<entry>
<title>Fix pkg-config .pc files with LibreSSL</title>
<updated>2021-06-08T11:19:39+00:00</updated>
<author>
<name>inoguchi</name>
<email></email>
</author>
<published>2021-06-08T11:19:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e8bab3c0a42f6b7f31c03997e897e41687efcfaa'/>
<id>urn:sha1:e8bab3c0a42f6b7f31c03997e897e41687efcfaa</id>
<content type='text'>
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@
</content>
</entry>
<entry>
<title>Make tree build again</title>
<updated>2016-09-03T12:42:47+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2016-09-03T12:42:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=98c68c607d98de6403940d47170aebf8f582f7ad'/>
<id>urn:sha1:98c68c607d98de6403940d47170aebf8f582f7ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Move build machinery for libcrypto from libssl/crypto to libcrypto, as well</title>
<updated>2014-04-11T22:51:54+00:00</updated>
<author>
<name>miod</name>
<email></email>
</author>
<published>2014-04-11T22:51:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=4362780bc2f199c11d5612e83851f6fc88139d21'/>
<id>urn:sha1:4362780bc2f199c11d5612e83851f6fc88139d21</id>
<content type='text'>
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.
</content>
</entry>
</feed>
