Ewald Jenisch <[email protected]> writes: > On one of my systems (FreeBSD 9.0 AMD64; kernel/system current as of > today; all ports up to date) chromium (ports/www/chromium) fails to compile. > > Here's what I get: > > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp: In function 'void > {anonymous}::S32_generic_D32_filter_DXDY_SSSE3(const SkBitmapProcState&, con > st uint32_t*, int, uint32_t*) [with bool has_alpha = true, uint32_t = > unsigned int]': > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:722:65: > instantiated from here > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:603:9: error: > '_mm_set1_epi16' was not declared in this scope > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:635:9: error: > '_mm_setzero_si128' was not declared in this scope > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:635:9: error: > '_mm_packus_epi16' was not declared in this scope > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:671:9: error: > '_mm_unpacklo_epi8' was not declared in this scope > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:688:9: error: > '_mm_add_epi16' was not declared in this scope > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:693:9: error: > '_mm_setzero_si128' was not declared in this scope > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:693:9: error: > '_mm_packus_epi16' was not declared in this scope > third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.cpp:696:9: error: > '_mm_cvtsi128_si32' was not declared in this scope > gmake: *** > [out/Release/obj.target/skia_opts_ssse3/third_party/skia/src/opts/SkBitmapProcState_opts_SSSE3.o] > Error 1 > gmake: *** Waiting for unfinished jobs.... > *** Error code 1
If you had looked a little earlier in the output, you would have gotten a bit more of a clue from the compiler. > Stop in /usr/ports/www/chromium. > *** Error code 1 > > Stop in /usr/ports/www/chromium. > > > Please note that I cvsup-ed just a few minutes ago - also tried "make > distclean" followed by make - same result :-( > > Has anybody out there seen this problem before? Yes. Chromium currently depends on SSE3; the recommended way of enabling that appears to be setting CPUTYPE. I'm not sure what the implications are for build machines whose output might be used on a variety of hardware... _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
