KNOWN_BUGS: cmake libcurl.pc uses absolute library paths

Closes #6169
This commit is contained in:
Daniel Stenberg 2020-11-18 16:53:28 +01:00
Родитель ad4b608263
Коммит 192099333b
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 5CC908FDB71E12C2
1 изменённых файлов: 9 добавлений и 0 удалений

Просмотреть файл

@ -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.5 build on Linux links libcurl to libdl
15.6 uses -lpthread instead of Threads::Threads 15.6 uses -lpthread instead of Threads::Threads
15.7 generated .pc file contains strange entries 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 -lgcc -lgcc_s
See https://github.com/curl/curl/issues/6167 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