In the Debian rules file one can see that --no-force-sse2 is enabled for platforms which never have sse2 eg armhf
override_dh_auto_build:
#disable JIT assembler on powerpc/arm64 where it doesn't compile
#disable WTF_USE_3D_GRAPHICS on ARM where it doesn't compile
#disable forcing SSE2 on all other platforms
#http://www.mentby.com/Group/webkit-qt-list/qtwebkit-231-tagged.html
ifneq (,$(filter arm64 powerpc ppc64el,$(DEB_HOST_ARCH))) ./Tools/Scripts/build-webkit --qt DEFINES+=ENABLE_JIT=0 DEFINES+=ENABLE_YARR_JIT=0 DEFINES+=ENABLE_ASSEMBLER=0
else ifeq ($(DEB_HOST_ARCH),armhf) ./Tools/Scripts/build-webkit --qt DEFINES+=ENABLE_JIT=0 DEFINES+=ENABLE_YARR_JIT=0 DEFINES+=ENABLE_ASSEMBLER=0 DEFINES+=WTF_USE_3D_GRAPHICS=0
else ./Tools/Scripts/build-webkit --qt --no-force-sse2
endif
There should be a test eg grep sse2 /proc/cpuinfo for i386 and amd64 to see if sse2 is available, and if not, then the --no-force-sse2 should also be added to the build options.
Why has the maintainer of the package not responded to this bug in nearly 2 years with this simple fix?
In the Debian rules file one can see that --no-force-sse2 is enabled for platforms which never have sse2 eg armhf
override_ dh_auto_ build: www.mentby. com/Group/ webkit- qt-list/ qtwebkit- 231-tagged. html $(DEB_HOST_ ARCH)))
./Tools/ Scripts/ build-webkit --qt DEFINES+ =ENABLE_ JIT=0 DEFINES+ =ENABLE_ YARR_JIT= 0 DEFINES+ =ENABLE_ ASSEMBLER= 0 HOST_ARCH) ,armhf)
./Tools/ Scripts/ build-webkit --qt DEFINES+ =ENABLE_ JIT=0 DEFINES+ =ENABLE_ YARR_JIT= 0 DEFINES+ =ENABLE_ ASSEMBLER= 0 DEFINES+ =WTF_USE_ 3D_GRAPHICS= 0
./Tools/ Scripts/ build-webkit --qt --no-force-sse2
#disable JIT assembler on powerpc/arm64 where it doesn't compile
#disable WTF_USE_3D_GRAPHICS on ARM where it doesn't compile
#disable forcing SSE2 on all other platforms
#http://
ifneq (,$(filter arm64 powerpc ppc64el,
else ifeq ($(DEB_
else
endif
There should be a test eg grep sse2 /proc/cpuinfo for i386 and amd64 to see if sse2 is available, and if not, then the --no-force-sse2 should also be added to the build options.
Why has the maintainer of the package not responded to this bug in nearly 2 years with this simple fix?