Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#7433 closed defect (fixed)

libaomenc.c: undeclared symbol AOM_ERROR_RESILIENT_PARTITIONS

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

Description

Building ffmpeg with libaom fails in libavcodec/libaomenc.c:744:109: error: 'AOM_ERROR_RESILIENT_PARTITIONS' undeclared here (not in a function); did you mean 'AOM_ERROR_RESILIENT_DEFAULT'?

                          " is still done over the partition boundary.",       0, AV_OPT_TYPE_CONST, {.i64 = AOM_ERROR_RESILIENT_PARTITIONS}, 0, 0, VE, "er"},
                                                                                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                                                                                             AOM_ERROR_RESILIENT_DEFAULT

Attached archive of logs and other diagnostic files was generated by media-autobuild_suite (running in MSYS2/MinGW)

Attachments (1)

logs.zip (214.7 KB ) - added by LigH 6 years ago.
MABS logs and diagnostics archive

Download all attachments as: .zip

Change History (9)

by LigH, 6 years ago

Attachment: logs.zip added

MABS logs and diagnostics archive

comment:1 by Cubittus, 6 years ago

I too see this issue with libaom git master head.

It is due to this libaom commit yesterday: 'Remove vestigial VP8 token partition support.'

https://aomedia.googlesource.com/aom/+/df4ffb73140fe31bebdabd17c1a7b53721e74838%5E%21/

comment:2 by LigH, 6 years ago

Added a reply to their code review 70421.

comment:3 by Carl Eugen Hoyos, 6 years ago

Keywords: libaom added

comment:4 by Carl Eugen Hoyos, 6 years ago

For future tickets: Please do not attach compressed logs, instead provide the simplified configure line you tested, run make V=1 twice and post the console output of the second run here. (Never post the console output of the first run.)

comment:5 by James, 6 years ago

Resolution: fixed
Status: newclosed

comment:6 by Hendrik, 6 years ago

Resolution: fixed
Status: newclosed

comment:7 by qrerw, 6 years ago

This problem still exists in 4.0.3

comment:8 by James, 6 years ago

The fix commit wasn't backported for it, but will be in 4.0.4

Note: See TracTickets for help on using tickets.