[Ffmpeg-devel] [PATCH] Move BeOS-specific code into os_support.c

François Revol revol
Tue Nov 14 14:56:23 CET 2006


> I set up a BeOS box over the weekend so I could test my patches that 
> I've 
> been trying to get accepted here. I can test this for you tonight 
> when I 
> get home.
> 
> Two things I've found tho with BeOS: the stock compiler is gcc 2.95.3 
> which doesn't seem to want to compile ffmpeg.  I upgraded to gcc 
> 3.4.x (I 
> believe it's 3.4.4, I can check when I get home) but when compiling I 
> get:
> 

while gcc3 should be ok to create non-gui binaries (BeOS GUI uses C++, 
so isn't compatible with gcc3's ABI), it is recommended to use a 2.9.
You should probably try this one:
http://bebits.com/app/4011

> cabac.h:522: error: can't find a register in class `GENERAL_REGS` 
> while 
> reloading `asm'

This is a tipical side effect of pushing gcc to its limits and you'll 
always find something in ffmpeg that breaks with every possible version 
of gcc.
The tipical workaround is to manually compile the specific file with -
O0 and/or without -g.

> I get this same error with MingW when I compile on Windows.  When I 
> use 
> the MingW cross compiler on Linux, I don't get this error at all.  
> Both 

Because it's not the exact same version and the register allocator is 
more robust in the cross version likely.

> Also in the configure script, the first set of lines under "make sure 
> we 
> are running under a compatible shell" have to be commented out to 
> work on 
> BeOS and MingW compiled under MSys on Windows.

BeOS R5 uses bash 2.03 at least (Zeta uses 3.0), so there should be no 
problem here.

Fran?ois.




More information about the ffmpeg-devel mailing list