hi, i was just updating my Thinkpad x31 and discovered ffmpeg used the above settings, which might break stuff on "not so recent" hardware or hardware that doesn't support those features... SOLUTION: Just ISUE="3dnow 3dnowext ..." Reproducible: Always Actual Results: package might not compile/work at all Expected Results: correct compilation + work as expected
I think this is invalid - this ebuild set things up in following way: - it tells ffmpeg configure to run it's processor features detection tests and enable detected - if a processor useflag is set, do nothing, if it's unset, disable feature, even if detected
Let's see what our video-herd guys think about this...
(In reply to comment #1) > I think this is invalid - this ebuild set things up > in following way: > - it tells ffmpeg configure to run it's processor > features detection tests and enable detected > - if a processor useflag is set, do nothing, > if it's unset, disable feature, even if detected > Exactly.
It makes more sense if you look at the ebuild: # CPU features for i in mmx ssse3 altivec ; do use $i || myconf="${myconf} --disable-$i" done use mmxext || myconf="${myconf} --disable-mmx2" use 3dnow || myconf="${myconf} --disable-amd3dnow" use 3dnowext || myconf="${myconf} --disable-amd3dnowext" so configure has a disable option, meaning, if you leave it on, no harm done.
sorry for the trouble! I thought with USE="3dnow" it would automatically compile with "--enable-3dnow", but as i understand now this is not the case.
