Building qt5-gui port?

[Mark Millard]

On 2019-Feb-10, at 10:32, Steve Kargl <sgk at troutmask.apl.washington.edu> wrote:

> On Sun, Feb 10, 2019 at 10:24:43AM -0800, Mark Millard wrote:
>> 
>> My reference to building for armv7 not having a problem in
>> my builds is an example of a 32-bit-target context for
>> qt5-gui. So i386 specific or some other aspect of how its
>> build was attempted might be involved in your context.
>> 
> 
> Do you use -march=native -mtune=native with clang in
> freebsd-current on all those architectures?

On none of them. But I do use (as appropriate to
each arm context that I target):

-mcpu=cortex-a7
-mcpu=cortex-a53
-mcpu=cortex-a57

I've not tried to have cpu/architecture tailored builds
for amd64 or powerpc64. (cortext-a7 is an armv7 example.
The other two are aarch64 examples.)

> I can build qt5-gui with "-march=i486", "-march=i686"
> "-march=i686 -mmmx", "-march=i686 -mmmx -msse".  I'll
> be adding each of -msse2, -msse3, -mssse3, -mcx16,
> -mfxsr, and -msahf to CFLAGS to see which one is causing
> the problem.
> 
> If adding all of the -target-feature options turned on
> by core2 work with i686, I'll then up i686 and repeat.
> 
> In the end, this looks like a "wrong code" issue with
> llvm/clang/clang++.
> 


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)