Building qt5-gui port?

Tijl Coosemans tijl at FreeBSD.org
Tue Mar 12 17:27:42 UTC 2019


On Tue, 12 Mar 2019 14:01:18 -0300 Lucas Nali de Magalhães
<rollingbits at gmail.com> wrote:
>> On Feb 11, 2019, at 2:05 PM, Steve Kargl <sgk at troutmask.apl.washington.edu> wrote:
>>> On Mon, Feb 11, 2019 at 10:08:08AM +0100, Tijl Coosemans wrote:
>>> On Sun, 10 Feb 2019 15:18:20 -0800 Steve Kargl
>>> <sgk at troutmask.apl.washington.edu> wrote:
>>>> On Sun, Feb 10, 2019 at 03:14:15PM -0800, Mark Millard wrote:
>>>>> 
>>>>> /usr/ports/Mk/Uses/qt-dist.mk has:
>>>>> 
>>>>> .    if ${ARCH} == i386 && empty(MACHINE_CPU:Msse2)
>>>>> CONFIGURE_ARGS+=        -no-sse2
>>>>> .    endif
>>>> 
>>>> Hmmm.  Oh well.  I set CPUTYPE=core2 in /etc/make.conf.
>>>> During configure of qt5-gui, it does try to use sse2,
>>>> sse3, ssse3, and even the unsupported avx.  The build
>>>> still dies.
>>> 
>>> You probably need to build all of Qt with the same flags, starting
>>> with qt5-qmake and then the other dependencies of qt5-gui.
>> 
>> Yes, that is what I decided to do.  Unfortnately, I decided
>> to use CPUTYPE=core2 to update kernel and world.  It seems a
>> recent change in FreeBSD-current has broken the drm-legacy-kmod
>> port, so no Xorg on the laptop, so no need for qt5 ports. :-)
> 
> I'm using the dirty hack
> 
> --- Makefile    (revision 495009)
> +++ Makefile    (working copy)
> @@ -36,6 +36,8 @@
>  # are using the obsolete 'register' key word.
>  CONFIGURE_ARGS+=       -c++std c++14
>  
> +CPUTYPE=i686
> +
>  USE_LDCONFIG=  ${PREFIX}/${QT_LIBDIR_REL}
>  
>  BUILD_WRKSRC=  ${WRKSRC}/src/${PORTNAME}
> 
> to compile and install the port. My patch isn't portable, I know. I saw
> an update to it and tried the new version: same error. I'm using
> CPUTYPE=native everywhere else, last FreeBSD 12.0-RELEASE-p3. The cpu
> is a Celeron M (Yonah). Let me know if you need more info.

native is not a valid value for CPUTYPE.  It is used in
/usr/share/mk/bsd.cpu.mk to determine cpu features, not just to set
-march= flag.  You can set CPUTYPE=yonah.


More information about the freebsd-ports mailing list