Opened 9 years ago

Closed 8 years ago

#48649 closed defect (fixed)

qgis install fails due to qt4-mac/qt5-mac conflict

Reported by: fhgwright (Fred Wright) Owned by: Veence (Vincent)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: manuel.deljesuspe@…, f.macports@…, petrrr, macports@…
Port: qgis

Description

A recent "upgrade outdated" triggered an error attempting to install qt5-mac as a dependency of gpsbabel, due to its conflicting with the installed qt4-mac. After removing qt4-mac and its dependencies, the gpsbabel upgrade worked, but it's now not possible to reinstall qgis due to its dependency on qt4-mac. With any luck, it can be updated to use qt5-mac instead, though there may be complications with the py27-qt4 and py27-qscintilla dependencies as well.

More generally, it would be nice to have a better way to handle versioned dependencies than the situation typified by this.

Attachments (1)

main.log (199.6 KB) - added by fhgwright (Fred Wright) 8 years ago.
Logfile from failed build

Download all attachments as: .zip

Change History (10)

comment:1 Changed 9 years ago by manuel.deljesuspe@…

Cc: manuel.deljesuspe@… added

Cc Me!

comment:2 Changed 9 years ago by f.macports@…

Cc: f.macports@… added

Cc Me!

comment:3 Changed 9 years ago by mf2k (Frank Schima)

Cc: vince@… removed
Owner: changed from macports-tickets@… to vince@…

comment:4 Changed 9 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:5 Changed 9 years ago by macports@…

I believe QGIS 2.8+ supports Qt5:

https://www.qgis.org/en/site/forusers/visualchangelog28/index.html#feature-qt5-support

also looks like Qt4 may (??) no longer be supported on OS X from 10.11, according to comments on https://trac.macports.org/ticket/48129

Last edited 9 years ago by macports@… (previous) (diff)

comment:6 Changed 9 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:7 Changed 8 years ago by Veence (Vincent)

QGis installs correctly with Qt4. Unfortunately I can’t install Qt5 at that time, so I’ll test this as soon as I can.

comment:8 Changed 8 years ago by fhgwright (Fred Wright)

I was able to successfully install qgis +grass now, after uninstalling qwt52 to permit it to install the conflicting qwt61. I had no dependents for qwt52, so it was probably just a leftover from the earlier qgis install.

However, an attempted build of qgis +grass +qt5 failed in the configure phase. Here is what's probably the relevant logfile excerpt:

:info:configure CMake Error at cmake/FindQScintilla.cmake:58 (FILE):
:info:configure   file failed to open for reading (No such file or directory):
:info:configure 
:info:configure     /opt/local/libexec/qt5/include/Qsci/qsciglobal.h
:info:configure Call Stack (most recent call first):
:info:configure   CMakeLists.txt:309 (FIND_PACKAGE)
:info:configure 
:info:configure 
:info:configure -- Found QScintilla2: /opt/local/libexec/qt5/lib/libqscintilla2.dylib ()
:info:configure CMake Error at cmake/FindQCA.cmake:88 (message):
:info:configure   Could not find QCA >= 2.0.3
:info:configure Call Stack (most recent call first):
:info:configure   CMakeLists.txt:312 (FIND_PACKAGE)
:info:configure 
:info:configure 
:info:configure -- Configuring incomplete, errors occurred!

The qscintilla and qca packages are installed:

MacPro:~ fw$ port installed qscintilla
The following ports are currently installed:
  qscintilla @2.9.1_0 (active)
MacPro:~ fw$ port installed qca
The following ports are currently installed:
  qca @2.1.0_1+qt5 (active)

So the original problem reported in this ticket is in fact resolved, due to the ability of qt4 and qt5 to coexist, but qgis still doesn't work with qt5. That might deserve a new ticket (while closing this one).

I'll attach the complete logfile of the failure, anyway.

Changed 8 years ago by fhgwright (Fred Wright)

Attachment: main.log added

Logfile from failed build

comment:9 Changed 8 years ago by Veence (Vincent)

Resolution: fixed
Status: newclosed

QGis does not officially support Qt5 yet, and it seems to be a low priority task on the developers' team agenda. What I did here was only preliminary work to clear the path for a future version. I'll try to explore further and see if I can get a working build, but do not be hopeful of anything soon.

Note: See TracTickets for help on using tickets.