Seems like Chrome is having an issue with SSE3 (not? clang)

[Knight Of The Post]

On Tue, 2012-05-29 at 16:00 -0400, Lowell Gilbert wrote:
> "Edwin L. Culp W." <edwinlculp at gmail.com> writes:
> 
> > Seems like Chrome is having an issue with clang.  It starts with the
> > following errors:
> >
> >   CC(target)
> > out/Release/obj.target/skia_libtess/third_party/skia/third_party/glu/libtess/tess.o
> > In file included from
> > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:8:
> > /usr/include/clang/3.1/tmmintrin.h:28:2: error: "SSSE3 instruction set not
> > enabled"
> > #error "SSSE3 instruction set not enabled"
> >  ^
> >   CC(target)
> 
> I don't think it's clang; I'm getting the same thing under (I think) gcc
> 4.6. It seems like some SSE3-related flag isn't being set, but I don't
> have time to look at it more closely at the moment.  I think this is
> related to the latest update, since SSE3 became required in that
> update. I *do* have SSE3 -- some of the early amd64 chips didn't, but
> most do, and mine reports that it does.

I ran into the same error.(with both clang & gcc)
Adding -msse4 to the CFLAGS in the Makefile made it build past this
point and is just finished completely.

// i.e
CFLAGS+=        -Wno-error -msse4
//

I came across this very old hint;
http://lists.cs.uiuc.edu/pipermail/llvmbugs/2010-March/012017.html
Doesn't say it's the same bug though...

Regards,
Dre


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120530/928afc3b/attachment.pgp