even after using mmx flag compile of mplayer fails.please assist. Reproducible: Always
Created attachment 149423 [details] build.log
(In reply to comment #0) > even after using mmx flag compile of mplayer fails.please assist. The following snippet points to bad ram/faulty processor being the culprit. ffv1.c: In function 'decode_frame': ffv1.c:1013: internal compiler error: in hash_rtx, at cse.c:2436 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions.
Does it fail in the same place every single time?
(In reply to comment #3) > Does it fail in the same place every single time? > I guess so i wil try to compile it once again and provide you with the update.I have libxml also failing on me.It clearly fails with hardware or os warning message.but i am wondering if the issue is with the hardware why do some program compile and some do not ?
(In reply to comment #2) > (In reply to comment #0) > > even after using mmx flag compile of mplayer fails.please assist. > > The following snippet points to bad ram/faulty processor being the culprit. > > ffv1.c: In function 'decode_frame': > ffv1.c:1013: internal compiler error: in hash_rtx, at cse.c:2436 > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://bugs.gentoo.org/> for instructions. > +================= I am not sure peter i understand what do you mean by preprocessed source. I have attached build.log what else do you want me to provide you ?If you could point me somewhere it would be great.
(In reply to comment #5) > I am not sure peter i understand what do you mean by preprocessed source. I > have attached build.log what else do you want me to provide you ?If you could > point me somewhere it would be great. Dear Amit, this symptom is quite common on broken or overclocked hardware. Please provide an answer to comment #3 (ie. try to emerge mplayer several times in a row and tell us if it breaks in the same place each time). After you've done this, please reopen this bug.