Opened 5 weeks ago

Closed 3 weeks ago

#6731 closed defect (fixed)

build no longer works: ERROR: libbluray not found using pkg-config

Reported by: hydra3333 Owned by:
Priority: important Component: build system
Version: git-master Keywords:
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Summary of the bug:
A "standard" build had worked for months, but no longer does, now throwing error
ERROR: libbluray not found using pkg-config
config log to be attached

ffmpeg version:
built on 2017.10.14

Attachments (2)

ffmpeg_config.log (458.5 KB) - added by hydra3333 5 weeks ago.
ffmpeg config log
libbluray.pc (698 bytes) - added by hydra3333 5 weeks ago.
the libbluray .pc file as amended

Download all attachments as: .zip

Change History (15)

Changed 5 weeks ago by hydra3333

ffmpeg config log

Changed 5 weeks ago by hydra3333

the libbluray .pc file as amended

comment:1 Changed 5 weeks ago by hydra3333

oh, cross-compiled under ubuntu as static for used on win10 x64, using a variation of rdp's build script.

comment:2 Changed 5 weeks ago by hydra3333

I see this thread https://patchwork.ffmpeg.org/patch/5540/ already seems to refer to this and related build errors, apparently newly arising from something like

"extralibs no longer being global after this merge".

comment:3 Changed 5 weeks ago by jamrial

  • Component changed from undetermined to build system
  • Priority changed from normal to important
  • Version changed from unspecified to git-master

libbluray's pkg-config file seems to currently be insufficient to resolve all its dependencies.

The issue has been reported there already. See https://mailman.videolan.org/pipermail/libbluray-devel/2017-October/002855.html

comment:4 Changed 5 weeks ago by hydra3333

Thank you. In the interim, it seems it (and related matters) can be addressed in part by an appropriate end-user configure, please refer here -

http://ffmpeg.org/pipermail/ffmpeg-devel/2017-October/217981.html

comment:5 Changed 5 weeks ago by jamrial

libbluray seems to have fixed it in http://git.videolan.org/?p=libbluray.git;a=commitdiff;h=bd887f4e9d8e81f2656fe0d0494bf20af852a23c

It should be available in their next release.

comment:6 Changed 5 weeks ago by hunnypuppy

It seems to still fail but with a different error now:

patching file configure.ac
Hunk #1 FAILED at 27.

comment:7 Changed 5 weeks ago by jamrial

I'm not sure what you're trying to do, but the above is a commit from libbluray.

Assuming you built libbluray from source, you can recompile it from git head after fetching the above commit. Otherwise wait for them to tag a release and your distro or package manager to update to it.

comment:8 Changed 5 weeks ago by hunnypuppy

hmm, I'm building using the ffmpeg build helpers rdp script to build it. I removed the sources and had it re-download the git and compile and I'm still seeing that error.

I believe the script is doing

git clone https://git.videolan.org/git/libbluray.git <folder>
get fetch
git checkout -f master
git merge origin/master

Anything else required?

Last edited 5 weeks ago by hunnypuppy (previous) (diff)

comment:9 Changed 5 weeks ago by jamrial

That error is something trying to patch configure.ac from libbluray. Probably the script you mention you're using.

It's unrelated to the issue at hand and you should look at it with whoever wrote the script.

comment:10 Changed 5 weeks ago by hunnypuppy

I just nuked the whole sandbox and tried a fresh build from scratch and it worked. Looks like something was left over outside the libburay source folder which the script was trying to reference.

Thanks! It's working now.

Last edited 5 weeks ago by hunnypuppy (previous) (diff)

comment:11 Changed 5 weeks ago by hunnypuppy

I just nuked the whole sandbox and tried a fresh build from scratch and it worked. Looks like something was left over outside the libbluray source folder which the script was trying to reference.

Thanks! It's working now.

Last edited 5 weeks ago by hunnypuppy (previous) (diff)

comment:12 Changed 3 weeks ago by CoRoNe

I believe this ticket is now fixed and thus can be closed.

comment:13 Changed 3 weeks ago by jamrial

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.