> On Tue, Jul 07, 2009 at 09:02:01AM +0200, Oliver Seitz wrote:
>> {standard input}:30: Error: `ff_h264_mlps_state+128(%eax)' is not a
>> valid
>> 64 bit base/index expression
>
> Now that is funny.
> This can only come from cabac.h, line 505:
> "movzbl "MANGLE(ff_h264_mlps_state)"+128("ret"), "tmp" \n\t"
> Where "ret" is %0 from an asm block with these constraints:
> :"=&a"(bit)
> :"r"(state), "r"(c)
> : "%"REG_c, "%ebx", "%edx", "%esi", "memory"
>
> The only way this can end up as eax is that the compiler thinks it is
> compiling for 32 bit instead of 64 bit - though that should give far
> more errors.
There are more... But I thought it would be of no use to post all 572
errors on a mailing list as I think the errors will not describe the real
problem.
> Are you using a working compiler or maybe the FreeBSD
> people applied some patches they didn't understand?
There seems to be only one patch on the compiler port:
Index: libjava/Makefile.in
===================================================================
--- libjava/Makefile.in (revision 117734)
+++ libjava/Makefile.in (working copy)
@@ -712,7 +712,7 @@
$(am__append_2) $(am__append_3)
toolexecmainlib_DATA = libgcj.spec
dbexec_LTLIBRARIES = libjvm.la
-pkgconfigdir = $(libdir)/pkgconfig
+pkgconfigdir = $(prefix)/libdata/pkgconfig
jardir = $(datadir)/java
jar_DATA = libgcj-$(gcc_version).jar libgcj-tools-$(gcc_version).jar
@JAVA_HOME_SET_FALSE@JAVA_HOME_DIR = $(prefix)
It doesn't look like it can cause those symptoms, does it?
_______________________________________________
MPlayer-users mailing list
MPlayer-users@xxxxxxxxxxxx
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
