[Gstreamer-bugs] [Bug 136658] Changed - gst-ffmpeg : asm compilation problem

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=136658

Changed by thomas at apestaart.org.

--- shadow/136658	Mon Mar 15 18:28:26 2004
+++ shadow/136658.tmp.12863	Tue Mar 16 05:00:23 2004
@@ -57,6 +57,73 @@
 
 
 ------- Additional Comments From bugs at leroutier.net  2004-03-15 18:28 -------
 Created an attachment (id=25680)
 build log when it works (building it manually after autoregen with params)
 
+
+------- Additional Comments From thomas at apestaart.org  2004-03-16 05:00 -------
+a few observations on the first one:
+
+a)
+ * Patching ${S}/gst-libs/ext/ffmpeg/ltmain.sh...
+ *   Could not apply portage.patch!
+ *   Please verify that it is not needed.
+ * Cannot apply any patch, running libtoolize...
+ * Patching ${S}/ltmain.sh...
+ *   Could not apply portage.patch!
+ *   Please verify that it is not needed.
+ * Cannot apply any patch, running libtoolize...
+
+1) why is it trying to do these patches ?
+2) why does it run libtoolize ?
+
+IMO it shouldn't be trying to do this.
+
+b) I cannot see the line it uses to run configure.  What does it use ?
+c) 
+There's a clear warning in the configure run:
+configure: WARNING: If you wanted to set the --build type, don't use
+--host.
+    If a cross compiler is detected then cross compile mode will be used.
+
+I think this probably should be heeded, ie don't use --host
+
+d) there are some more problems further down during configure:
+checking whether stripping libraries is possible... yes
+./configure: line 20638: test: too many arguments
+checking math.h usability... yes
+checking math.h presence... yes
+checking for math.h... yes
+checking for log... no
+checking for log in -lm... yes
+checking whether compiler understands -Wall... yes
+./configure: line 21437: test: too many arguments
+
+maybe check what's being tested on those two lines in configure
+
+e) This part is giving the error:
+f /bin/sh ../../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
+-I../.. -I../../libavcodec -DHAVE_AV_CONFIG_H=1   -msse -O0 -ggdb -MT
+libmmxsse_la-dsputil_mmx.lo -MD -MP -MF
+".deps/libmmxsse_la-dsputil_mmx.Tpo" -c -o libmmxsse_la-dsputil_mmx.lo
+`test -f 'dsputil_mmx.c' || echo './'`dsputil_mmx.c; \
+then mv -f ".deps/libmmxsse_la-dsputil_mmx.Tpo"
+".deps/libmmxsse_la-dsputil_mmx.Plo"; else rm -f
+".deps/libmmxsse_la-dsputil_mmx.Tpo"; exit 1; fi
+ gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../libavcodec
+-DHAVE_AV_CONFIG_H=1 -msse -O0 -ggdb -MT libmmxsse_la-dsputil_mmx.lo
+-MD -MP -MF .deps/libmmxsse_la-dsputil_mmx.Tpo -c dsputil_mmx.c  -fPIC
+-DPIC -o .libs/libmmxsse_la-dsputil_mmx.o
+dsputil_mmx.c: In function `h263_h_loop_filter_mmx':
+dsputil_mmx.c:614: error: can't find a register in class
+`GENERAL_REGS' while reloading `asm'
+make[8]: *** [libmmxsse_la-dsputil_mmx.lo] Erreur 1
+
+You said it seems the only difference seems to be -O0 -ggdb right ?
+Maybe try to use this line manually in that dir, but use -O2 like you
+do in the other one, and see if that works.  If it does, you can be
+reasonably sure it's a problem with these cflags, but I'm not yet
+convinced.
+
+Basically, the thing to do is to compare both outputs, and compare the
+differences in environment and invocation between the two runs.