Date: Sun, 10 Feb 2019 10:24:43 -0800 From: Mark Millard <marklmi@yahoo.com> To: sgk@troutmask.apl.washington.edu Cc: =?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= <rollingbits@gmail.com>, ports-list freebsd <freebsd-ports@freebsd.org> Subject: Re: Building qt5-gui port? Message-ID: <FFA352D4-39FC-4BCC-A5E8-00076A78A543@yahoo.com> In-Reply-To: <20190210151427.GB34772@troutmask.apl.washington.edu> References: <2EF34E75-DDBC-4D99-B317-3C8F20725AE5@yahoo.com> <6AFE3B36-FBFA-46AA-81DB-31BB24A5D75E@gmail.com> <20190210151427.GB34772@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Feb-10, at 07:14, Steve Kargl <sgk at = troutmask.apl.washington.edu> wrote: > On Sun, Feb 10, 2019 at 11:34:28AM -0200, Lucas Nali de Magalh=C3=A3es = wrote: >>>=20 >>> My lumina builds indirectly build qt5-qui and have been having Dumb typo on my part: should have been a qt5-gui reference. >>> no problems (targeting amd64, aarch64, armv7, and powerpc64). >>> (My powerpc64 context is not normally gcc 4.2.1 based.) >>>=20 >>> [...] >>=20 >> So it looks like it's 32bit specific; maybe i386 only. >>=20 >=20 > Yes, likely. >=20 > I'll note that valgrind hass been broken for a long time,=20 > now that I think about it was built with -march=3Dnative. >=20 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. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FFA352D4-39FC-4BCC-A5E8-00076A78A543>