Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian "make" Problems #253

Closed
Infiziert90 opened this issue Nov 15, 2016 · 10 comments
Closed

Debian "make" Problems #253

Infiziert90 opened this issue Nov 15, 2016 · 10 comments

Comments

@Infiziert90
Copy link

Hiho,

System: Debian Jessie 64bit

i get tons of errors and warnings in the newest Build again ...
./configure runs without any warning or error
but make ...
http://sprunge.us/OEff

@Infiziert90 Infiziert90 changed the title Debian "make" Problems with .cpp Debian "make" Problems Nov 15, 2016
@dubhater
Copy link

You probably need ffmpeg instead of libav. Alternatively, pass --disable-subtitle to configure.

@Infiziert90
Copy link
Author

configure: WARNING: unrecognized options: --disable-subtitle

@dubhater
Copy link

dubhater commented Jan 5, 2017

Oops. It's --disable-subtext.

@Infiziert90
Copy link
Author

thx worked for me ...

and i'm using ffmpeg
ffmpeg version 3.2.2-1~bpo8+1 Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 4.9.2 (Debian 4.9.2-10)

@dubhater
Copy link

dubhater commented Jan 6, 2017

I have ffmpeg 3.2.2 as well (compiled from https://ffmpeg.org/releases/ffmpeg-3.2.2.tar.xz, unpatched). The subtext plugin compiled fine.

Does pkg-config --cflags libavutil give you the right path?

@Infiziert90
Copy link
Author

Infiziert90 commented Jan 6, 2017

Nop ... it shows me a empty line

but
root@Debian-82-jessie-64-LAMP ~/# whereis libavutil
libavutil: /usr/include/libavutil

@dubhater
Copy link

dubhater commented Jan 7, 2017

An empty line probably means the pkg-config file says -I/usr/include. pkg-config doesn't print that because the compiler will look in that folder anyway.

If your ffmpeg package was installed in /usr and /usr/include/libavutil belongs to it, then I don't know what's wrong. If your ffmpeg package was installed elsewhere, then you need to invoke VapourSynth's configure like this: PKG_CONFIG_PATH='/your_ffmpeg_packages_libdir/pkgconfig' ./configure

@Infiziert90
Copy link
Author

root@Debian-82-jessie-64-LAMP ~/# whereis libavutil
libavutil: /usr/include/libavutil

its the same path ... so i think its a bug from vapoursynth
also its not a problem from me alone, ubuntu server shows the same issue with subtitle renderer

@myrsloik myrsloik reopened this Jan 8, 2017
@Infiziert90
Copy link
Author

A clean build of the latest stable release of ffmpeg solves my problem. It seems to be a problem with the ffmpeg build in the Debian/Ubuntu repository.

@Infiziert90
Copy link
Author

Actually I built the latest snapshot, not the release. No idea if it would have worked with the release, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants