Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 May 2019 20:54:17 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 237745] Mk/Uses/qt-dist.mk: fix qt5 with GCC architectures
Message-ID:  <bug-237745-7788-InAaV7LAE8@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-237745-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-237745-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237745

--- Comment #15 from commit-hook@freebsd.org ---
A commit references this bug:

Author: tcberner
Date: Sat May 25 20:53:14 UTC 2019
New revision: 502634
URL: https://svnweb.freebsd.org/changeset/ports/502634

Log:
  MFH: r499101 r499116 r502628

  Fix build when using GCC. Needed by GCC architectures.

  Tested for no breakage on amd64 with Clang.

  PR:   235921
  Reviewed by:  tcberner
  Approved by:  tcberner (mentor)

  devel/qt5: Follow-up to r499101

  - Move the GCC related path fix into freebsd-g++/qmake.conf
    Otherwise the inclusion of the GCC path would break clang
    based systems when gcc-${GCC_DEFAULT} was installed.

  - This might break GCC architectures again, and if so, that
    will be fixed in a follow up commit.

  PR:           235921

  qt5: fix build on gcc architectures

  - the sed call was only replacing one of the %%LOCALBASE%% by ${LOCALBASE=
},
    due to the missing 'g' flag to the sed call.

  - with this change the gcc architectures should be able to build Qt5 agai=
n.

  PR:           237745
  Submitted by: Mark Millard <marklmi26-fbsd@yahoo.com>, jwb
  Reported by:  pkubaj

  Approved by:  ports-secteam (joneum via irc)

Changes:
_U  branches/2019Q2/
  branches/2019Q2/Mk/Uses/qt-dist.mk
  branches/2019Q2/devel/qt5/files/extrapatch-mkspecs_freebsd-g++_qmake.conf
  branches/2019Q2/devel/qt5-qmake/Makefile

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237745-7788-InAaV7LAE8>