Skip to content

Stop forcing pkgconfig static mode in configure - #823

Merged
pabuhler merged 1 commit into
cisco:mainfrom
Hashim1999164:fix/pkg-config-static-only-when-static
Sep 9, 2026
Merged

Stop forcing pkgconfig static mode in configure#823
pabuhler merged 1 commit into
cisco:mainfrom
Hashim1999164:fix/pkg-config-static-only-when-static

Conversation

@Hashim1999164

@Hashim1999164 Hashim1999164 commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes #822

configure was rewriting PKG_CONFIG to always pass static mode. That pulls private link flags into the OpenSSL discovery probes, so hosts whose libcrypto.pc names private archives that are not installed (for example Ubuntu with libjitterentropy) fail with cannot find compatible openssl crypto lib.

This change leaves pkgconfig in its normal dynamic mode for discovery. Libs.private in the generated libsrtp3.pc file still receives the resulting LIBS values.

Test plan

  • Ran ./configure with OpenSSL on macOS; crypto probes succeed
  • Ran make and make runtest; all libsrtp3 and crypto self tests passed

Unconditional --static made OpenSSL discovery pull Libs.private into
link probes, which fails when those private archives are not installed.
@pabuhler
pabuhler merged commit e38387e into cisco:main Sep 9, 2026
46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

autotools configure fails on Ubuntu because pkg-config is forced into static mode

2 participants