[FFmpeg-user] Compiling source on RHEL 5.4
Reindl Harald
h.reindl at thelounge.net
Wed Nov 21 01:05:18 CET 2012
not only at build time
they are dynamically linked and you have zero
chance to link everything static
take a look at ./configure --help and try to disable as
much can (not needed for you) to reduce the deps and
consult the "ldd" command on the other machine for deps
see below
[harry at srv-rhsoft:~]$ ldd /usr/bin/ffmpeg
linux-vdso.so.1 => (0x00007fff1b2f9000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f482753a000)
libxvidcore.so.4 => /lib64/libxvidcore.so.4 (0x00007f4827223000)
libvpx.so.1 => /lib64/libvpx.so.1 (0x00007f4826f77000)
libvorbisenc.so.2 => /lib64/libvorbisenc.so.2 (0x00007f4826aa8000)
libvorbis.so.0 => /lib64/libvorbis.so.0 (0x00007f482687b000)
libtheoraenc.so.1 => /lib64/libtheoraenc.so.1 (0x00007f482663e000)
libtheoradec.so.1 => /lib64/libtheoradec.so.1 (0x00007f4826428000)
libschroedinger-1.0.so.0 => /lib64/libschroedinger-1.0.so.0 (0x00007f4826157000)
librtmp.so.0 => /lib64/librtmp.so.0 (0x00007f4825f3c000)
libz.so.1 => /lib64/libz.so.1 (0x00007f4825d23000)
libopenjpeg.so.3 => /lib64/libopenjpeg.so.3 (0x00007f4825b03000)
libopencv_core.so.2.3 => /lib64/libopencv_core.so.2.3 (0x00007f482570d000)
libopencv_imgproc.so.2.3 => /lib64/libopencv_imgproc.so.2.3 (0x00007f4825293000)
libmp3lame.so.0 => /lib64/libmp3lame.so.0 (0x00007f482501d000)
libgsm.so.1 => /lib64/libgsm.so.1 (0x00007f4824e11000)
libfreetype.so.6 => /usr/lib64/freetype-freeworld/libfreetype.so.6 (0x00007f4824b6f000)
libfaac.so.0 => /lib64/libfaac.so.0 (0x00007f4824957000)
libm.so.6 => /lib64/libm.so.6 (0x00007f482465b000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f482444b000)
libc.so.6 => /lib64/libc.so.6 (0x00007f4824094000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4827770000)
libogg.so.0 => /usr/lib64/libogg.so.0 (0x00007f4823e8c000)
liborc-0.4.so.0 => /lib64/liborc-0.4.so.0 (0x00007f4823c11000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f482390e000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f48236f8000)
libgnutls.so.26 => /lib64/libgnutls.so.26 (0x00007f4823440000)
libgcrypt.so.11 => /lib64/libgcrypt.so.11 (0x00007f48231c8000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f4822fc3000)
librt.so.1 => /lib64/librt.so.1 (0x00007f4822dbb000)
libtbb.so.2 => /lib64/libtbb.so.2 (0x00007f4822b8e000)
libmp4v2.so.0 => /lib64/libmp4v2.so.0 (0x00007f48228d6000)
libtasn1.so.3 => /lib64/libtasn1.so.3 (0x00007f48226c5000)
libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007f48224c0000)
libp11-kit.so.0 => /lib64/libp11-kit.so.0 (0x00007f48222ae000)
libgomp.so.1 => /lib64/libgomp.so.1 (0x00007f482209f000)
Am 21.11.2012 00:59, schrieb Emily W Watt:
> Ok, based on your response I am assuming that my failure to run the
> compiled binary of ffmpeg 1.0 on my kernel/OS release is not a problem I
> can fix. I don't disagree that I will need the libraries to build -- the
> only solution I have come up with is to manually download the libraries
> individually, without using yum. I have not been able to find a good source
> and list of all dependencies/libraries without using SVN.
>
> On Tue, Nov 20, 2012 at 3:46 PM, Reindl Harald <h.reindl at thelounge.net>wrote:
>
>>
>>
>> Am 21.11.2012 00:43, schrieb Emily W Watt:
>>> I do not have the option of building the daily repository snapshots, as
>>> those require use of yum and an external web connection to download all
>> the
>>> libraries and dependencies that I don't have access to with my closed
>>> network.
>>
>> and how should this work at all without the libraries?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-user/attachments/20121121/ba2da3d5/attachment.asc>
More information about the ffmpeg-user
mailing list