Steven M. Schultz wrote:
> On Fri, 19 Jan 2007, Marco Behnke wrote:
> 
> 
>>ok, I mastered that step on the ladder.... this on is a "big & nasty" one...
> 
> 
>>Making all in yuvcorrect
> 
>       ...
> 
>>if gcc -DHAVE_CONFIG_H -I. -I. -I..  -I.. -I/usr/local/include 
>>-I../utils   -march=pentium3 -mtune=pentium3 -g -O2 -no-cpp-precomp 
>>-D_THREAD_SAFE  -Wall -Wunused -MT yuvcorrect_functions.o -MD -MP -MF 
>>".deps/yuvcorrect_functions.Tpo" -c -o yuvcorrect_functions.o ...
> 
> 
>       Which model of MacIntel do you have?  I thought Apple was using
>       recent Intel cpus and not old Pentium3 cpus - I am not sure that
>       "-march=pentium3 -mtune=pentium3" is correct for a Intel based MAC
> 
> 
>>yuvcorrect_functions.c: In function 'yuvcorrect_chrominance_init':
>>yuvcorrect_functions.c:704: error: unrecognizable insn:
>>(insn:HI 166 165 167 10 yuvcorrect_functions.c:698 (set (reg:V4SI 144)
> 
> 
>       line 698 is 
>        
>                  *(u_c_p++) = (uint8_t) newU;
> 
>       if gcc  can not compile something that simple then the compiler
>       is broken :(
> 
> 
>>yuvcorrect_functions.c:704: internal compiler error: in extract_insn, at 
> 
> 
>       Line  704 is the '}' at the end of the function 
>       yuvcorrect_chrominance_init.
> 
> 
>>Sadly I have to register for money to submit bugs to apple..... anyone 
> 
> 
>       Oh, there is a 'feedback' link that you can submit a complaint or 
>       report to - but it will be ignored :(
> 
>       The only things I can think of to try are edit the yuvcorrect/Makefile
>       and delete all the "-mtune" and "-march" options - maybe the mismatch
>       the actual cpu type (I do not think Apple is using pentium3 cpus)

That worked for me ! Thanks a lot.
Finally
I got my self-compiled binary

>       and the option is causing the problem.  THe other thing to try is
>       change all "-O2" to be "-O1" - sometimes the compiler bug is in the
>       optimizer area.
> 
> 
>>had this before? Maybe anyone have a binary for mac intel?
> 
> 
>       No, no one has seen this before.  BUT, if the compiler is broken how
>       do you expect anyone to have a binary for mac intel? ;)



> 
>       All of my Macs are PPC based - I do not have a Intel based Mac (yet).
>       It is time to update/replace the Powerbok... ;)

Stay away as long as you can ;) We had the first horror when we found
out that we have to switch to gcc 4 as gcc 3.3 isn't allowed to compile
binaries on mac intel.

> 
>       Cheers,
>       Steven Schultz
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Mjpeg-users mailing list
> Mjpeg-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mjpeg-users


-- 
Portrix.net
z. Hd. Marco Behnke
Stresemannstr. 375
22761 Hamburg

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to