From: Daniel Stenberg <daniel@haxx.se>
Date: Wed, 18 Nov 2020 15:53:28 +0000 (+0100)
Subject: KNOWN_BUGS: cmake libcurl.pc uses absolute library paths
X-Git-Tag: curl-7_74_0~57
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=192099333b8c6c1da894e08c3471befd67225730;p=thirdparty%2Fcurl.git

KNOWN_BUGS: cmake libcurl.pc uses absolute library paths

Closes #6169
---

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index cab9fb4e58..5a9b1bf70c 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -128,6 +128,7 @@ problems may have been fixed or changed somewhat since this was written!
  15.5 build on Linux links libcurl to libdl
  15.6 uses -lpthread instead of Threads::Threads
  15.7 generated .pc file contains strange entries
+ 15.8 libcurl.pc uses absolute library paths
 
 ==============================================================================
 
@@ -874,3 +875,11 @@ problems may have been fixed or changed somewhat since this was written!
  -lgcc -lgcc_s
 
  See https://github.com/curl/curl/issues/6167
+
+15.8 libcurl.pc uses absolute library paths
+
+ The libcurl.pc file generated by cmake contains things like Libs.private:
+ /usr/lib64/libssl.so /usr/lib64/libcrypto.so /usr/lib64/libz.so. The
+ autotools equivalent would say Libs.private: -lssl -lcrypto -lz
+
+ See https://github.com/curl/curl/issues/6169