[Bug 229260] devel/qt5-core: fails (configure) when using LOCALBASE != /usr/local

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229260

Tobias C. Berner  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

--- Comment #5 from Tobias C. Berner  ---
I don't quite get how you even get to try building Qt5 with non standard prefix
as quite a few of the dependencies already do not support it. 

However, Qt5 is now patched to sed in the value of ${LOCALBASE} when building
qt-base. This hopefully should get you further.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 229260] devel/qt5-core: fails (configure) when using LOCALBASE != /usr/local

2019-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229260

--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:

Author: tcberner
Date: Sat Apr  6 15:21:42 UTC 2019
New revision: 498144
URL: https://svnweb.freebsd.org/changeset/ports/498144

Log:
  devel/qt5-qmake: override hardocded value of localbase with ${LOCALBASE}

  - The qmake.conf shipped with Qt5 sets /usr/local by default. This patch
replaces that string with the value of ${LOCALBASE} to ease use with
different prefixes.

  PR:   229260

Changes:
  head/Mk/Uses/qt-dist.mk
  head/devel/qt5/files/extrapatch-mkspecs_freebsd-clang_qmake.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 229260] devel/qt5-core: fails (configure) when using LOCALBASE != /usr/local

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229260

--- Comment #3 from John Hein  ---
Yes, it still fails the same way.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 229260] devel/qt5-core: fails (configure) when using LOCALBASE != /usr/local

2019-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229260

Tobias C. Berner  changed:

   What|Removed |Added

  Flags|maintainer-feedback?(kde@Fr |maintainer-feedback+
   |eeBSD.org)  |
 CC||tcber...@freebsd.org

--- Comment #2 from Tobias C. Berner  ---
Hi John

What's the status of this now, is it still failing?


mfg Tobias

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 229260] devel/qt5-core: fails (configure) when using LOCALBASE != /usr/local

2018-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229260

John Hein  changed:

   What|Removed |Added

 CC||z7dr6ut...@snkmail.com

--- Comment #1 from John Hein  ---
I didn't mean to include 'pcre2' in the path in the patch in the previous
comment.

--- mkspecs/freebsd-clang/qmake.conf.orig   2018-06-19 23:00:56.0 -0600
+++ mkspecs/freebsd-clang/qmake.conf
@@ -8,8 +8,8 @@
 include(../common/bsd/bsd.conf)

 # Addon software goes into /usr/local on FreeBSD, by default we will look
there
-QMAKE_INCDIR_POST   = /usr/local/include
-QMAKE_LIBDIR_POST   = /usr/local/lib
+QMAKE_INCDIR_POST   = /opt/include
+QMAKE_LIBDIR_POST   = /opt/lib

 QMAKE_LFLAGS_NOUNDEF= -Wl,--no-undefined

-- 
You are receiving this mail because:
You are the assignee for the bug.

maintainer-feedback requested: [Bug 229260] devel/qt5-core: fails (configure) when using LOCALBASE != /usr/local

2018-06-23 Thread bugzilla-noreply
Bugzilla Automation  has asked k...@freebsd.org for
maintainer-feedback:
Bug 229260: devel/qt5-core: fails (configure) when using LOCALBASE !=
/usr/local
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229260



--- Description ---
If you build with LOCALBASE != /usr/local, devel/qt5-core (and probably other
qt ports) fails to configure:

 .
 .
  Using system PCRE2 . no
 .
 .
Project ERROR: Library 'pcre2' is not defined.
*** Error code 3

Stop.
make: stopped in /usr/ports/devel/qt5-core


If you change the references in
/lib/qt5/mkspecs/freebsd-clang/qmake.conf that contain the
hard-coded /usr/local to the value of the non-default LOCALBASE, then the
configure is able to find pcre2.  For example:

--- mkspecs/freebsd-clang/qmake.conf.orig   2018-06-19 23:00:56.0 -0600
+++ mkspecs/freebsd-clang/qmake.conf
@@ -8,8 +8,8 @@
 include(../common/bsd/bsd.conf)

 # Addon software goes into /usr/local on FreeBSD, by default we will look
there
-QMAKE_INCDIR_POST   = /usr/local/include
-QMAKE_LIBDIR_POST   = /usr/local/lib
+QMAKE_INCDIR_POST   = /opt/pcre2/include
+QMAKE_LIBDIR_POST   = /opt/pcre2/lib

 QMAKE_LFLAGS_NOUNDEF= -Wl,--no-undefined


I'm sure that's not the only way to address the problem.  Note that that
qmake.conf file is owned by the devel/qt5-qmake port, of course, not
devel/qt5-core.


[Bug 229260] devel/qt5-core: fails (configure) when using LOCALBASE != /usr/local

2018-06-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229260

Bug ID: 229260
   Summary: devel/qt5-core: fails (configure) when using LOCALBASE
!= /usr/local
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: Individual Port(s)
  Assignee: k...@freebsd.org
  Reporter: z7dr6ut...@snkmail.com
 Flags: maintainer-feedback?(k...@freebsd.org)
  Assignee: k...@freebsd.org

If you build with LOCALBASE != /usr/local, devel/qt5-core (and probably other
qt ports) fails to configure:

 .
 .
  Using system PCRE2 . no
 .
 .
Project ERROR: Library 'pcre2' is not defined.
*** Error code 3

Stop.
make: stopped in /usr/ports/devel/qt5-core


If you change the references in
/lib/qt5/mkspecs/freebsd-clang/qmake.conf that contain the
hard-coded /usr/local to the value of the non-default LOCALBASE, then the
configure is able to find pcre2.  For example:

--- mkspecs/freebsd-clang/qmake.conf.orig   2018-06-19 23:00:56.0 -0600
+++ mkspecs/freebsd-clang/qmake.conf
@@ -8,8 +8,8 @@
 include(../common/bsd/bsd.conf)

 # Addon software goes into /usr/local on FreeBSD, by default we will look
there
-QMAKE_INCDIR_POST   = /usr/local/include
-QMAKE_LIBDIR_POST   = /usr/local/lib
+QMAKE_INCDIR_POST   = /opt/pcre2/include
+QMAKE_LIBDIR_POST   = /opt/pcre2/lib

 QMAKE_LFLAGS_NOUNDEF= -Wl,--no-undefined


I'm sure that's not the only way to address the problem.  Note that that
qmake.conf file is owned by the devel/qt5-qmake port, of course, not
devel/qt5-core.

-- 
You are receiving this mail because:
You are the assignee for the bug.