Michel Dänzer wrote:
Remember, endianness is not the only difference. PPC also assumes unsigned char (ARM too). That has caused headaches in other programs before which were endian-clean, e.g. gnome-pim and gnucash, and from the number of warnings during my last E 0.16.x build of the type "Warning: branch never reached due to limited range of data type," I'm surprised there have been no big bugs there. (Though with gnucash, we thought it was not char-safe, so the maintainer was passing -funsigned-char, but it was, so there was a conflict with the C libraries... that one was tough to find!)Siggi Langauf wrote:On Tue, 28 Aug 2001, Michel Dänzer wrote:Siggi Langauf wrote: Also, I was excited at first to see that it has an ffmpeg plugin, but I couldn't play MJPEG nor DivX files, is that to be expected?This is expected to work, but I think ffmpeg still has some problems on big endian machines. Any volunteers are welcome ;-)The strange thing is that it said it couldn't find a decoder for both file types, even though it showed the correct ID (verified with xanim, which plays the MJPEG files). Endianness bug with the type detection?
Zeen, -- -Adam P. GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6Welcome to the best software in the world today cafe! <http://lyre.mit.edu/%7Epowell/The_Best_Stuff_In_The_World_Today_Cafe.ogg>