Opened 3 years ago

Closed 3 years ago

Last modified 3 weeks ago

#8258 closed defect (invalid)

configure script ignores pkgconfigdir

Reported by: Vortico Owned by:
Priority: normal Component: undetermined
Version: git-master Keywords:
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no


Using --pkgconfigdir when running ./configure appears to have no effect on the actual PKG_CONFIG_PATH.

To reproduce, install a library, like libopus, which places an opus.pc file in a default location like /usr/lib/pkgconfig/. Then move opus.pc to a nonstandard directory such as /home/vortico/local/lib/pkgconfig/, forcing us to use pkgconfigdir. Run the following in ffmpeg's directory.

./configure --pkgconfigdir=/home/vortico/local/lib/pkgconfig/ --enable-libopus

The script fails with

ERROR: opus not found using pkg-config

However, running

PKG_CONFIG_PATH=/home/vortico/local/lib/pkgconfig/ ./configure --enable-libopus

is successful. In the test_pkg_config() function in configure, the line

test_cmd $pkg_config --exists --print-errors $pkg_version

or other invocations of pkg_config, appears to not make use of the pkgconfigdir at all.

Change History (5)

comment:1 by Timo R., 3 years ago

--pkgconfigdir controls where "make install" will install ffmpegs .pc files. It has no influence on where it searches for them in any way.

As configure --help says:
"--pkgconfigdir=DIR install pkg-config files in DIR [LIBDIR/pkgconfig]"

comment:2 by Carl Eugen Hoyos, 3 years ago

Resolution: invalid
Status: newclosed

comment:3 by Jason Pepas, 3 weeks ago


Last edited 3 weeks ago by Jason Pepas (previous) (diff)

comment:4 by Jason Pepas, 3 weeks ago


Last edited 3 weeks ago by Jason Pepas (previous) (diff)

comment:5 by Jason Pepas, 3 weeks ago

this turned out to be a problem local to my system, sorry for the confusion.

Last edited 3 weeks ago by Jason Pepas (previous) (diff)
Note: See TracTickets for help on using tickets.