slackware 64 curent: question on official ffmpeg slack build
by jr_bob_dobbs from LinuxQuestions.org on (#577EE)
I decided to recompile ffmpeg. Yes, I am aware that ffmpeg is now included in Slackware Current. I wanted to add in some extra codecs. So as not to mess things up, I'm using Patrick's slackbuild and the same version of the package source.
To verify what codecs were actually being used by ffmpeg, I modified the official slackbuild so that it logged the output of the ./configure phase for later perusal. The change made is in the last line of the ./configure, from:
Code: $wavpack || exit 1to
Code: $wavpack > "${CWD}/config_log.txt" || exit 1So I ran the slackbuild.
What is interesting is this excerpt from the resulting configure log:
Code:install prefix /usr
source path .
C compiler gcc
C library glibc
ARCH x86 (generic)
big-endian no
runtime cpu detection yesMy system is 64bit. Patrick's slackbuild is setting the ARCH parameter in the usual way, so shouldn't that be saying 'x86_64' not 'x86'?
I am wondering, is ffmpeg compiling for 64 bit? Or is compilng both 32 bit and 64 bit in one binary and then its run-time CPU detection is choosing which parts to execute?
I then used this test on one of the actual binaries to try to ascertain:
Code:$ readelf -l ffmpeg | grep ': /lib'
[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]So I *guess* that ffmpeg is 64 bit and that it's just a small error in the ./configure output? This has me scratching my head.
Thank you.
To verify what codecs were actually being used by ffmpeg, I modified the official slackbuild so that it logged the output of the ./configure phase for later perusal. The change made is in the last line of the ./configure, from:
Code: $wavpack || exit 1to
Code: $wavpack > "${CWD}/config_log.txt" || exit 1So I ran the slackbuild.
What is interesting is this excerpt from the resulting configure log:
Code:install prefix /usr
source path .
C compiler gcc
C library glibc
ARCH x86 (generic)
big-endian no
runtime cpu detection yesMy system is 64bit. Patrick's slackbuild is setting the ARCH parameter in the usual way, so shouldn't that be saying 'x86_64' not 'x86'?
I am wondering, is ffmpeg compiling for 64 bit? Or is compilng both 32 bit and 64 bit in one binary and then its run-time CPU detection is choosing which parts to execute?
I then used this test on one of the actual binaries to try to ascertain:
Code:$ readelf -l ffmpeg | grep ': /lib'
[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]So I *guess* that ffmpeg is 64 bit and that it's just a small error in the ./configure output? This has me scratching my head.
Thank you.