Opened 10 years ago
Closed 10 years ago
#4549 closed defect (invalid)
/usr/bin/ld: libavutil/color_utils.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
Reported by: | Kai Hendry | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | unspecified | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug: Build error http://ix.io/itN
How to reproduce: The following PKGBUILD on Archlinux: http://ix.io/itO
Notice I've added
--enable-vaapi \
--enable-hwaccel=h264 \
--enable-pic \
Change History (5)
comment:1 by , 10 years ago
comment:3 by , 10 years ago
Is there an easy way to binary search through 38 switches of configure? Good news is that I managed to build with just:
./configure \
--prefix=/usr \
--enable-vaapi \
--enable-libx264 \
--enable-gpl \
--enable-hwaccel=h264
So some combination with the existing options of https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/ffmpeg mixed in with Intel hardware acceleration that I'm looking for creates the issue. Argh. :(
To make matters worse, enabling VAAPI on my Intel Broadwell laptop seems to make ZERO time difference encoding h264. Sigh.
comment:4 by , 10 years ago
To make matters worse, enabling VAAPI on my Intel Broadwell laptop seems to make ZERO time difference encoding h264. Sigh.
You seem to be under the mistaken impression that ffmpeg has support for vaapi encoding.
comment:5 by , 10 years ago
Component: | avutil → undetermined |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Please reopen if you can explain how to reproduce this issue.
The error message you have shown usually implies that you didn't run make distclean
before building FFmpeg.
I cannot reproduce.
To make this a valid ticket please provide the minimal configure line needed to reproduce the error (some options in your configure line have no effect). Then run make until you see the mentioned error. Run "make V=1" afterwards and provide the complete, uncut console output of your last run of make.