SIEGERSTEIN wrote:
В сообщении от Tuesday 23 October 2007 05:12:28 SIEGERSTEIN написал(а):
[encode_x264.so] using cpu capabilities: MMX MMXEXT SSE SSE2 3DNow!
Floating point exception
$
OK. I understand. By default, transcode compile with 3DNow! support:
$ ./configure --help
...
--enable-mmx enable MMX code portions (yes)
--enable-3dnow enable 3DNow code portions (yes)
--enable-sse enable SSE code portions (yes)
--enable-sse2 enable SSE2 code portions (yes)
--enable-altivec enable Altivec code portions (yes)
...
May be so "Floating point exception" is take effect?
I have Intel Pentium Presott Processor, so there is no 3DNow! instruction.
I recompile transcode with --disable-3dnow, but take the same result.
Is this right option? Why it not working? Why encode_x264.so build with 3DNow!
support ?
Best,
There is a 3dnow use flag for the transcode ebuild, you most likely had
it turned on.
$ emerge gentookit
$ equery uses transcode
Also make sure the CFLAGS in make.conf are set correctly. Mainly that
your -march or -mcpu flags are appropriate and there's no flags there
trying to turn on 3dnow support.
Also for me the transcode 1.1.0alpha4 is in portage, it is just masked
for testing. You will need to do:
$ echo "=media-video/transcode-1.1.0_alpha4" >> /etc/portage/package.unmask
$ echo "media-video/transcode ~x86" >> /etc/portage/package.keywords
That will unmask transcode 1.1.0alpha4 and also tell portage you want to
use the unstable version (which 1.1.0alpha4 is also marked as). After
that portage won't try to downgrade your transcode installation.
Shawn
