Date: Wed, 30 May 2012 22:03:29 +0200 From: Knight Of The Post <knightotp@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: Seems like Chrome is having an issue with SSE3 (not? clang) Message-ID: <1338408209.4472.142.camel@bully.hofman.it> In-Reply-To: <44vcje3gh6.fsf@lowell-desk.lan> References: <CALFgp2PyisN7Sc3_CM0O7-SwgLaNk7AW%2BprZmtnNCYtn1og-3Q@mail.gmail.com> <44vcje3gh6.fsf@lowell-desk.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-4mgd1wnJvZf/OMi/Zdxr Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Tue, 2012-05-29 at 16:00 -0400, Lowell Gilbert wrote: > "Edwin L. Culp W." <edwinlculp@gmail.com> writes: >=20 > > 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/li= btess/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) >=20 > 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+=3D -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 --=-4mgd1wnJvZf/OMi/Zdxr Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJPxn0RAAoJEH4rhYAi0yjOw4UH/iJHE4s2+V3wC5+5LU07dPvY 6s2iGzea3dsql7OCvLmIo908LUxhAbH9CU7xiPTps95eeKvoxh3fG3H06knXn7o7 b4aVRZzcuMHoCzruhQfUIc1Rrly4mEu9/eY/7OEgmdQA2/wkWDRwZpW+HrQ2tnTC 5oUxr60ZzJch/SYwDMS/2QBNAdXRrjwtaXCD5uuk0gW3tQ5WynLnzK464TTE+jS8 5RHFxqMT2Vf1eUYFTRGcVzyl16dHr+vRfoQ4FBtGBFUSV9IinfE8nw063MuTG1ka MANBiTYbGsJJeREcWagWBDs/JiFiZwuNXRg16KPYnP9Tp+1jci2zabev7k560H8= =CYba -----END PGP SIGNATURE----- --=-4mgd1wnJvZf/OMi/Zdxr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1338408209.4472.142.camel>