[FFmpeg-trac] #4197(build system:new): libspeex detection is broken on systems without pkg-config

FFmpeg trac at avcodec.org
Mon Dec 22 00:40:30 CET 2014

#4197: libspeex detection is broken on systems without pkg-config
             Reporter:  cehoyos      |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:  build
              Version:  git-master   |  system
             Keywords:  libspeex     |               Resolution:
  regression                         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |

Comment (by cehoyos):

 Replying to [comment:12 Cigaes]:
 > Replying to [comment:11 cehoyos]:
 > > I don't understand: Why should something that does work fine for x264
 not work for other libraries?
 > I want to get rid of it for x264 too! But for x264, it is already there,
 for speex, it has been removed, and I object it coming back.

 The patch was not reviewed and since libspeex is not completely outdated,
 we should really allow installation without jumping through the pkg-config

 > > Could you elaborate?
 > configure takes a lot of time, blocking for the rest of the build

 Could you elaborate how the patch made configure faster or how the
 workaround would make it slower?

 > > Of course.
 > > I opened this ticket because I consider this issue a (severe)
 > And I consider it good riddance: configure is faster, simpler, more
 readable, more reliable.

 I don't think it is faster and calling removing a feature being more
 reliable is hard to understand for me.

 > > I meant the build system, sorry for the wrong wording.
 > Then of course they can install something on the build system: they are
 installing ffmpeg.

 I never install FFmpeg.

 > > I mean every user who is not an admin on the build system. Note that
 yasm is not needed on all targets.
 > Actual practical examples, please.

 yasm is not needed on arm and powerpc.

 > > Please understand while for you (as for many other FFmpeg developers)
 it is completely clear how to use pkg-config, for me as for many users who
 post on the user mailing list it is needlessly difficult.
 > {{{sudo apt-get install pkg-config}}}

 This does not even work on my development system and it certainly doesn't
 work for people using servers where they are not admins.
 But I meant using pkg-config not installing it.

 > There is nothing more to do in normal cases. In non-normal cases, the
 user already did something way more complex than {{{export

 I consider this at least a magnitude more difficult than setting a path.

 > > Yes, I just want to be able to build (configure and build) FFmpeg with
 (most) external libraries without having to use pkg-config.
 > “without having to use pkg-config” is not a functional need.

 It is needed for my workflow and was very often requested by users on the
 user mailing list.

Ticket URL: <https://trac.ffmpeg.org/ticket/4197#comment:13>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list