Opened 4 years ago

Closed 2 years ago

#59689 closed defect (fixed)

qgis3 @3.10.0_0: fatal error: 'ui_qgswmssourceselectbase.h' file not found

Reported by: dershow Owned by: Veence (Vincent)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: gwright83, Dave-Allured (Dave Allured), mascguy (Christopher Nielsen)
Port: qgis3

Description

I have qgis3 3.8.3 installed and working. I just tried to upgrade to 3.10.0 and it fails. I've attached my log file.

Attachments (1)

main.log (7.7 MB) - added by dershow 4 years ago.

Change History (10)

Changed 4 years ago by dershow

Attachment: main.log added

comment:1 Changed 4 years ago by mf2k (Frank Schima)

Cc: Veence removed
Owner: set to Veence
Status: newassigned

comment:2 Changed 4 years ago by gwright83

I saw the same error as in the attached log this afternoon. Upgrade to 3.10.0 failed at the same point with the same message. Running Mojave 10.14.6; Macports 2.6.2.

comment:3 Changed 4 years ago by gwright83

I deactivated the previously installed version (3.8.3) and rebuilt. It ran to completion and started correctly.

Looks like an old library is snarfed by the new build, resulting in a failure. IIRC, this has been a problem with Qgis for a while. Is there any way to remind the user to deactivate previously installed versions before updating?

comment:4 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: gwright83 added
Summary: qgis3 upgrade to 3.10.0_0 failsqgis3 @3.10.0_0: fatal error: 'ui_qgswmssourceselectbase.h' file not found

Greg, it's not clear if the problem you experienced was the same as the one experienced by dershow, since you did not attach a main.log file. dershow's log says:

:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_qgis3/qgis3/work/QGIS-3_10_0/src/providers/wms/qgswmssourceselect.h:20:10: fatal error: 'ui_qgswmssourceselectbase.h' file not found
:info:build #include "ui_qgswmssourceselectbase.h"
:info:build          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Our buildbot, on which previous versions are never active when building, sees the same problem. So having a previous version active is not likely to have contributed to this problem.

It was also reported in homebrew (over 2 years ago!), but as a comment in a ticket about a different problem, and was therefore not addressed.

Later in the log, we see:

:info:build [  3%] Generating ui_qgswmssourceselectbase.h
:info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_qgis3/qgis3/work/build/src/ui && /opt/local/libexec/qt5/bin/uic -o /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_qgis3/qgis3/work/build/src/ui/ui_qgswmssourceselectbase.h /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_qgis3/qgis3/work/QGIS-3_10_0/src/ui/qgswmssourceselectbase.ui

So it's trying to use ui_qgswmssourceselectbase.h before having generated it. A classic parallel build problem. Veence, can you please report it to the developers of qgis3? We can work around it by disabling parallel building in the port until upstream fixes the dependencies of their build system:

use_parallel_build no

Until we do that, users can work around it with:

sudo port install qgis3 build.jobs=1

comment:5 Changed 4 years ago by Dave-Allured (Dave Allured)

Cc: Dave-Allured added

comment:6 Changed 2 years ago by mascguy (Christopher Nielsen)

It looks like qgis3 has been building fine for quite a while - with parallels builds enabled - and has been updated numerous times since this ticket was originally opened.

Is this still an issue?

comment:7 Changed 2 years ago by mascguy (Christopher Nielsen)

Cc: mascguy added

comment:8 Changed 2 years ago by dershow

I have switched over to just downloading the QGIS app from their website, so I haven't tested it in a while.

comment:9 Changed 2 years ago by mascguy (Christopher Nielsen)

Resolution: fixed
Status: assignedclosed

Let's close as fixed then. If anyone is still seeing this issue, we can reopen.

Note: See TracTickets for help on using tickets.