Re: wireshark 2.2.x build fail

2016-10-17 Thread Joe Marcus Clarke
On 10/16/16 18:56, Michael Butler wrote: On 10/16/16 11:36, Joe Marcus Clarke wrote: Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail

Re: wireshark 2.2.x build fail

2016-10-16 Thread Michael Butler
On 10/16/16 11:36, Joe Marcus Clarke wrote: Seems like the easy fix would be to incorporate the fix for this bug, and then disable SSE4.2 in a CFLAGS override. The better fix would be to have clang do the same as GCC so that the test build would fail on those platforms that don't support

Re: wireshark 2.2.x build fail

2016-10-16 Thread Joe Marcus Clarke
On 10/15/16 21:06, Michael Butler wrote: Just a "heads up": wireshark 2.2.x introduces the compiler flag "-msse4.2" via 'configure' if the compiler accepts that flag. The capability, or otherwise, of the host machine is ignored as it is expected that the one module in which GCC will use these

wireshark 2.2.x build fail

2016-10-15 Thread Michael Butler
Just a "heads up": wireshark 2.2.x introduces the compiler flag "-msse4.2" via 'configure' if the compiler accepts that flag. The capability, or otherwise, of the host machine is ignored as it is expected that the one module in which GCC will use these instructions has a run-time check.