Eric Marchionni wrote: > Paul Stear wrote: > >>> I had the same issue. Upon looking into it further it is a problem >>> with the mmx code not being configured correctly during the >>> configure process. I don't know enough to determine if it is in the >>> ebuild or the actual transcode code. But the workaround that I >>> found was to do the following: >>> >>> env USE="mmx" emerge transcode >>> >>> This enabled the ebuild to compile correctly on my box. >>> >>> Regards, >>> Paul >>> >>> > jep, thanks this really worked!! > but how did you figure out that mmx was the source of the problem? > just curious... > > -eric
I went into /var/tmp/portage/work/ and found the directory where it was being compiled. I copied the config.h file to /tmp and then did a make distclean to clean up portages attempts at compiling and configuring. I then ran ./configure and make to see if it compiled properly. When it did compile properly, I did a diff on the config.h file created when portage ran configure and the config.h when I ran configure. The difference was something like CONFIG_MMX=N vs CONFIG_MMX=Y (This wasn't exactly what was displayed, but is the gist of the differences) I then did an etcat -u transcode, which showed that the mmx USE flag was turned off. This led me to try setting the mmx USE flag with the emerge command. I honestly think the problem is with the ebuild, but I don't know enough to definitively determine that. Regards, Paul -- [EMAIL PROTECTED] mailing list
