Date: Sun, 10 Feb 2019 10:32:50 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Mark Millard <marklmi@yahoo.com> Cc: Lucas Nali de =?iso-8859-1?Q?Magalh=E3es?= <rollingbits@gmail.com>, ports-list freebsd <freebsd-ports@freebsd.org> Subject: Re: Building qt5-gui port? Message-ID: <20190210183250.GB35569@troutmask.apl.washington.edu> In-Reply-To: <FFA352D4-39FC-4BCC-A5E8-00076A78A543@yahoo.com> References: <2EF34E75-DDBC-4D99-B317-3C8F20725AE5@yahoo.com> <6AFE3B36-FBFA-46AA-81DB-31BB24A5D75E@gmail.com> <20190210151427.GB34772@troutmask.apl.washington.edu> <FFA352D4-39FC-4BCC-A5E8-00076A78A543@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? 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++. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190210183250.GB35569>