Unable to build ffmpeg-4.0 on fedora 20 release

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Unable to build ffmpeg-4.0 on fedora 20 release

jd1008
I would like to send the make output file to someone
who might want to look at all the warnings (deprecated calls), and errors.
Would someone please tell me where to upload the file or who to send it to.

Thanx!!

jd
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Unable to build ffmpeg-4.0 on fedora 20 release

Kieran O Leary
On Fri, 27 Apr 2018, 01:29 JD, <[hidden email]> wrote:

> I would like to send the make output file to someone
> who might want to look at all the warnings (deprecated calls), and errors.
> Would someone please tell me where to upload the file or who to send it to.


Can you not paste it into an email,or perhaps attach it if it is huge and
maybe copy paste the last few relevant lines into the body of the email?



> Thanx!!
>
> jd
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> [hidden email] with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Unable to build ffmpeg-4.0 on fedora 20 release

Reindl Harald
In reply to this post by jd1008


Am 27.04.2018 um 02:21 schrieb JD:
> I would like to send the make output file to someone
> who might want to look at all the warnings (deprecated calls), and errors.
> Would someone please tell me where to upload the file or who to send it to

what about to start with a supported operating system?

Fedora 26 will be EOL in around one month and you are takling about F20?
no there don't exist any excuse, if you can't cope with distr-upgrades
it's the wrong distribution
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Unable to build ffmpeg-4.0 on fedora 20 release

jd1008
In reply to this post by Kieran O Leary


On 04/26/2018 06:56 PM, Kieran O Leary wrote:
> On Fri, 27 Apr 2018, 01:29 JD, <[hidden email]> wrote:
>
>> I would like to send the make output file to someone
>> who might want to look at all the warnings (deprecated calls), and errors.
>> Would someone please tell me where to upload the file or who to send it to.
>
> Can you not paste it into an email,or perhaps attach it if it is huge and
> maybe copy paste the last few relevant lines into the body of the email?
OK, here are the errors:

libavutil/hwcontext_vaapi.c:1169:5: error: unknown type name ‘VABufferInfo’
      VABufferInfo buffer_info;
      ^
libavutil/hwcontext_vaapi.c: In function ‘vaapi_unmap_to_drm_abh’:
libavutil/hwcontext_vaapi.c:1189:5: error: implicit declaration of
function ‘vaReleaseBufferHandle’ [-Werror=implicit-function-declaration]
      vas = vaReleaseBufferHandle(hwctx->display, mapping->image.buf);
      ^
libavutil/hwcontext_vaapi.c: In function ‘vaapi_map_to_drm_abh’:
libavutil/hwcontext_vaapi.c:1246:25: error: request for member
‘mem_type’ in something not a structure or union
      mapping->buffer_info.mem_type =
                          ^
libavutil/hwcontext_vaapi.c:1284:5: error: implicit declaration of
function ‘vaAcquireBufferHandle’ [-Werror=implicit-function-declaration]
      vas = vaAcquireBufferHandle(hwctx->display, mapping->image.buf,
      ^
libavutil/hwcontext_vaapi.c:1296:32: error: request for member ‘handle’
in something not a structure or union
             mapping->buffer_info.handle);
                                 ^
libavutil/hwcontext_vaapi.c:1300:37: error: request for member ‘handle’
in something not a structure or union
          .fd   = mapping->buffer_info.handle,
                                      ^
cc1: some warnings being treated as errors
make: *** [libavutil/hwcontext_vaapi.o] Error 1

I know fc20 is unsupported, I do not want to upgrade it.

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Unable to build ffmpeg-4.0 on fedora 20 release

Reindl Harald


Am 27.04.2018 um 03:28 schrieb JD:

>
>
> On 04/26/2018 06:56 PM, Kieran O Leary wrote:
>> On Fri, 27 Apr 2018, 01:29 JD, <[hidden email]> wrote:
>>
>>> I would like to send the make output file to someone
>>> who might want to look at all the warnings (deprecated calls), and
>>> errors.
>>> Would someone please tell me where to upload the file or who to send
>>> it to.
>>
>> Can you not paste it into an email,or perhaps attach it if it is huge and
>> maybe copy paste the last few relevant lines into the body of the email?
> OK, here are the errors:
>                      ^
> libavutil/hwcontext_vaapi.c:1284:5: error: implicit declaration of
> function ‘vaAcquireBufferHandle’ [-Werror=implicit-function-declaration]

RTFM

-Wno-error=implicit-function-declaration

> I know fc20 is unsupported, I do not want to upgrade it

yeah - why didn't you then install CentOS to start with?
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Unable to build ffmpeg-4.0 on fedora 20 release

Mark Thompson
In reply to this post by jd1008
On 27/04/18 02:28, JD wrote:

> On 04/26/2018 06:56 PM, Kieran O Leary wrote:
>> On Fri, 27 Apr 2018, 01:29 JD, <[hidden email]> wrote:
>>
>>> I would like to send the make output file to someone
>>> who might want to look at all the warnings (deprecated calls), and errors.
>>> Would someone please tell me where to upload the file or who to send it to.
>>
>> Can you not paste it into an email,or perhaps attach it if it is huge and
>> maybe copy paste the last few relevant lines into the body of the email?
> OK, here are the errors:
>
> libavutil/hwcontext_vaapi.c:1169:5: error: unknown type name ‘VABufferInfo’
>      VABufferInfo buffer_info;
>      ^
> libavutil/hwcontext_vaapi.c: In function ‘vaapi_unmap_to_drm_abh’:
> libavutil/hwcontext_vaapi.c:1189:5: error: implicit declaration of function ‘vaReleaseBufferHandle’ [-Werror=implicit-function-declaration]
>      vas = vaReleaseBufferHandle(hwctx->display, mapping->image.buf);
>      ^
> libavutil/hwcontext_vaapi.c: In function ‘vaapi_map_to_drm_abh’:
> libavutil/hwcontext_vaapi.c:1246:25: error: request for member ‘mem_type’ in something not a structure or union
>      mapping->buffer_info.mem_type =
>                          ^
> libavutil/hwcontext_vaapi.c:1284:5: error: implicit declaration of function ‘vaAcquireBufferHandle’ [-Werror=implicit-function-declaration]
>      vas = vaAcquireBufferHandle(hwctx->display, mapping->image.buf,
>      ^
> libavutil/hwcontext_vaapi.c:1296:32: error: request for member ‘handle’ in something not a structure or union
>             mapping->buffer_info.handle);
>                                 ^
> libavutil/hwcontext_vaapi.c:1300:37: error: request for member ‘handle’ in something not a structure or union
>          .fd   = mapping->buffer_info.handle,
>                                      ^
> cc1: some warnings being treated as errors
> make: *** [libavutil/hwcontext_vaapi.o] Error 1
>
> I know fc20 is unsupported, I do not want to upgrade it.

Fixed for 4.0.1: <http://git.videolan.org/?p=ffmpeg.git;a=commit;h=44cb6474770e6603913cb76e3be4278f663aad3e>.

If you don't need VAAPI then you can work around it using --disable-vaapi (or --disable-autodetect).

Thanks,

- Mark
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".